If you already have an account, click Sign in and log in.
If you don’t have an account, create one by clicking Sign up. Enter a username, email, and password. Once you have an account, log in to GitHub with it.
The first time you log in to GitHub, you will be asked for verification via email. Once verified, you will be taken to your GitHub homepage.
Create a fork of the projects. A fork is simply a copy of a project into your own account, so that changes made to the copy do not affect the original project. To fork, click the Fork button in the top right corner of every GitHub project page.
Within a few seconds, a copy of the Urantiapedia projects will be created in your GitHub account. These projects are a new, complete copy that you can make any changes you need without affecting the original projects. Check that you have them by clicking on your user menu and selecting Your repositories to return to your account. You should see both projects and a message saying Forked from ….
Your forks of the two Urantiapedia projects (urantiapedia and urantiapedia-backup) are copies that GitHub does not automatically update. From the moment you create them, other users will be making changes to the original project, and those changes will not be automatically reflected in your projects. Your projects, remember, are an independent copy, and changes made to the copy or the original are not synchronized unattended to the other.
It is very important, therefore, that before making any changes to the files in your copies, you make sure that they are synchronized with the current state of the original projects.
To do this, before any work session (which is detailed in the following steps of this manual) you must follow these simple steps:
Click on each of your copies of the projects, and once in them click on the Sync fork option. You will be shown a menu indicating how many saves (commits) have been made to the original project that are not in your copy. In the image you can see that there are 4 saves that we do not have and therefore our copy is out-of-date (This branch is out-of-date). Simply click on Update branch to bring the changes in the original project to your copy.
Wait a few seconds while GitHub updates your copy. Once you’re done, if you click Sync fork again you’ll see that everything is up to date, indicating that the changes are not behind the original (This branch is not behind the upstream).
You’ll need to remember to do this for each project every time you want to start a change job. What can you do if you forget to do this? Normally nothing will happen as long as the files you’re going to modify haven’t already been modified. You can continue working without any problems and perform all the tasks indicated in the following steps of the manual, but it is highly recommended that you follow this safer practice of running these steps before any edits.