When your page files are complete, you can fold them from your own fork into the master organization content repository by sending me a pull request. You do this by navigating (on the github website) to your fork of the content repository. If it says “This branch is 1 commit ahead,” you can submit a pull request by clicking the “new pull request” button on the top left above your list of files. Follow the instructions and keep clicking until the pull request is submitted. I will then see the pull request and either merge your files into the organization’s content or request that you change something before doing so. If you want to check the status of your pull requests, scroll all the way to the top of the github web page. Click on “Pull requests” in white letters on a black background. You will then see a list of the pull requests you’ve submitted.
In the screenshot above, you’ll notice the caption “This branch is 1 commit ahead, 98 commits behind dig-eg-gaz:master.” The “commit ahead” is work that needs to be submitted in a pull request and merged. The “commits behind” represents work that your colleagues have done, and that has been merged into the master content repository but hasn’t made it to your fork yet. When it comes time to do your querying and analysis of others’ files, it’s very important to make sure that you are working on an up-to-date version of the content files. When you look at your fork of the
dig-eg-gaz/content repository on the github website, you will see a line comparing your repository to the organization repository: If you are ahead, click the “new pull request” button above the status report and ask the organization to merge your changes.
If you are behind:
These Github tutorials might be useful: