-
Create a GitHub account, and let Joe or Jeff know that you need to be added to the rcl-github organization. Provided you are in digital initiatives, let Channing know that you need to be added to the Digital Initiatives team.
-
Install GitHub desktop
-
Open and Log into Github Desktop using your new GitHub credentials
-
Select File>Clone Repository
-
Using the dialog that appears, select the repository you want to add. Note that you only need to clone a repository the very first time you work on a given project on a particular computer.
Note: If you cannot see a repository that you know exists, it means EITHER that it was created after you opened this dialog, you were granted permission to it after you opened this dialog (in either case, refreshing will suffice), OR that you do not have permission to view the repository, in which case you most likely are not in the rochester-rcl organization on GitHub.
-
Immediately prior to any work, open github desktop, select the repository in question, and click "Fetch Origin". If you don't have the project in your "Current repository" dropdown, you will need to clone it first (see above).
This ensures that the copy of the project on your local computer is up to date with any changes that have been made by others.
-
Your github client should now look something like this:
Click EITHER the button for "Open the repository in your external editor," or "view the files of your repository in explorer" at your choice.
-
Make your changes locally using any software installed on your system, but do NOT move any files to outside the top level folder that GitHub desktop has created for the project on your system. Only changes within that folder will be tracked.
-
When you are done making changes, review the changes made in GitHub desktop's interface.
-
Once satisfied, write up a summary and description of your changes, and hit "Commit to master" (it may say commit to main, or some other word/ phrase after "commit to", that's fine)
-
Finally, hit "push origin" once you have made all changes in your sitting.
If you would like to add more points that can be rolled back to, make each point an individual commit. There is no need to push every time you commit. Just make sure that you DO push, as pushing is the act that actually updates the version of the project seen by others.
Be vigilant about Fetching, Committing, and Pushing frequently. Git gets much more complicated if you don't!
If you have questions, concerns, or strange behavior, please reference this document for a more in depth guide on Git, or ask Channing.
If you would like help on setting up change control for a new set of files, a new project, or new repository, please speak to Channing for assistance until you are familiar with the process.
Please look for places to use Git/Github wherever possible, as it allows for a much safer way of storing work history and allows for much greater collaboration.