Jump to content

Managing your mod repository using Git(hub) and branches


niektb
 Share

Recommended Posts

I thought it might be a good idea to explain to you how to make the most of your git(hub) repository and work effectively in a team or make sure your master branch is always clean and stable.

That's where one of git's most powerful feature comes in: branching. Let's kick right off!

In this tutorial I'll be using the Github for Windows client as I experienced it to be intuitive and user-friendly. Also I'll use Aristeia as example.

Righto, in your program create a new branch. Do so by clicking the '+' button as shown in the image below:

post-15513-0-51755000-1426534791_thumb.p

Give it a name and the program should show something like this:

post-15513-0-57241100-1426534792_thumb.p

Make the changes you want. Now we need to publish the branch to make it available to others (you can also make changes after you published your newly created branch):

post-15513-0-32705400-1426534796_thumb.p

Open your browser and go to you Github page, if you did everything correctly you can now see your branch online:

post-15513-0-34007700-1426534797_thumb.p

If you think your changes are ready to commit, click on the green 'Compare & pull request' button. After that your screen should show something like this:

post-15513-0-51596500-1426534798_thumb.p

Give it a name and a description and click on the 'create pull request' button. There you go, a pull request is created and it directly offers a discussion thread. Other team members are also notified of your pull request:

post-15513-0-64769600-1426534799_thumb.p

If other people noticed bugs you can append new commits in your github for windows client. If they think the pull request is good enough they can merge it (or you can do it yourselves if you have the rights to do so):

post-15513-0-52490100-1426534800_thumb.p

Tada! :yess: You're changes have landed into the master branch! You can now delete your branch or use it for further development (and create a new pull request over time)

Edited by niektb
  • Like 3
Link to comment
Share on other sites

Pull = get something

Push = send something

Commit = give a version number to some change

Not sure what fetch is, or when you need it

For Branch, you have to know that every repo has at least one branch (usually the Master branch). You can copy a branch into a new branch. That way you can work on something, without interrupting the master branch. When your work is done, you can merge the two branches again.

Link to comment
Share on other sites

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.

Guest
Reply to this topic...

×   Pasted as rich text.   Paste as plain text instead

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.

 Share

×
×
  • Create New...