Why would I want To Do This?
- Make an account with github if you don't have one yet.
- Navigate to the GCS Library repo. A repo, short for repository, is where code for programmers is stored. You don't need to know how to program to use the GCS Library repo though because the GCS application automatically makes the lib files for you.
- Once at the library repo, create a fork of the GCS Library. There should be a button in the top right that allows you to fork GCS. Forking in GIT gives you a copy of all the files in the library to work on by yourself so you can make changes as you like and when you are satisfied you can send them over to GCS for the dev to confirm or deny your changes.
- Once you have the fork set up, you can download it to your own PC to work on it, but you have two choices. If you like the commandline, then look here for what to do with your fork. If you prefer a GUI, then try SourceTree.
- If using source tree, setup the repositories for the repositories like this, making your fork the origin, and including the original repo (which I named Rich's Trunk in the screenshot) so that you can keep your fork up to date.
- Now That you have your fork setup, download the files wherever you want on your hard drive, you can choose the location in step 5, and edit the libraries in GCS. Add an item, advantage, template, etc.
- When you have finished your work, and it looks correct push it and commit it. The buttons are at the top of the SourceTree app, so it should be easy to figure out how.
- Now that your fork is updated online, create a pull request. A pull request is a way to tell the developer for GCS that you would like him to look at your change and include it. You can do this easily by looking for the origin remote in the section in the screenshot, right clicking on the one that matches the name you gave it and choosing create pull request.
- You are now done. Thanks for helping.