• Hey Guest! Ever feel like entering a Game Jam, but the time limit is always too much pressure? We get it... You lead a hectic life and dedicating 3 whole days to make a game just doesn't work for you! So, why not enter the GMC SLOW JAM? Take your time! Kick back and make your game over 4 months! Interested? Then just click here!
  • Hello [name]! Thanks for joining the GMC. Before making any posts in the Tech Support forum, can we suggest you read the forum rules? These are simple guidelines that we ask you to follow so that you can get the best help possible for your issue.

Discussion Local Source Control

W

Wardog

Guest
Today, I had my first "Whoops, I accidentally erased a good portion of my spritesheet" experience. Thankfully, this happened early on in my sprite creation, and got me to come across the concept of Source Control.

My question is how to set up a Source Control system local to my hard drive, without any online components.
(I did some searching online for tutorials on this, but they all seem to open with "Start a GitHub or BitBucket account.", and I don't want that).

I'm a solo dev, so I'm pretty much just looking to have an efficient backup/previous version catalog, that can save me a lot of hassle if I repeat the mistake I made today.

Also, with the local option, how would I go about generating an output of the changes made between two different versions of my game?

Thanks in advance for the advice.
 

Jack S

Member
Install GIT - I personally use Tortoise GIT for the windows shell extensions. Their are several free and paid GUI interfaces for GIT to choose from. You are not limited to the built in GIT features of GMS (personally I find them lacking, hence using the external tools)
 

FrostyCat

Redemption Seeker
I also agree with setting up Git. Contrary to popular opinion, getting a GitHub or BitBucket account is strictly optional. You can always set up a repository on the spot within the directory you're working in, then set up a remote target later if you need a backup online or in an external drive.

While you can certainly set up something like TortoiseGit for managing your working copies, it's worthwhile to learn at least some basic manoeuvres in the command line. Here are a few starters that you will likely use right away:

To set up a local repository:
Code:
cd "PROJECT DIRECTORY"
git init
git add .
git commit -m "Initial commit"
To check for changes since the last commit (summary of files):
Code:
git status
To check for changes since the last commit (line-by-line):
Code:
git diff
To commit your changes locally:
Code:
git add -A
git commit -m "COMMIT MESSAGE"
To view the history of changes in a GUI:
Code:
gitk
 
Top