Moving to Github


#21

oh good :slight_smile:

very similar to svn, just a slightly different workflow.

Here’s a quick rundown if you use the command line:

to initialize the repository (using S44Main as the example):
if you have a github account with a public key on file, grab it like this:

git clone git@github.com:spring1944/spring1944.git S44Main.sdd

if you do -not- have an account, and/or do not need commit access:

git clone https://github.com/spring1944/spring1944.git S44Main.sdd

That will put s44 into a directory called S44Main.sdd.

git status
[/code] is your most common command: it will tell you which files have changes that will be committed (or are new files which will be added, or files which were deleted), and which ones have changes that will -not- be committed. 

when you edit a file, to mark it as "to be committed" do [code]
git add units/ger/GERRifle.fbi

once that’s done, you can commit your changes with git commit -m 'Increased move speed for GERRifle'

that will save your changes in your local repository. to push them to the remote repository, do git push origin <branch> where is usually master

to pull in new changes from the remote repository, run git pull If you want, you can use git pull --rebase to “flatten” the git history, so your current (not yet pushed) commits will be jammed into the repo history as a flat line, rather than a branch. I usually do this.

Of course, you can also use windows.github.com/ which wraps all of this stuff in a nice UI. I haven’t used it personally, but I know several people who like it a lot.


#22

Ok, I’ve closed commit access on sourceforge for everyone: the repositories are still readable, but you can’t commit or create new ones. Onwards to a brighter future!