1. For CSE 3902, by Matt Boggus Intended mainly as reading material
GitHub notes
For CSE 3902, by Matt Boggus
Intended mainly as reading material

2. Before proceeding
Refer to the other slideset on source code control if your team is using the Visual Studio Online (other aliases for it in reference materials include: Team Foundation Server, Visual Studio Team Services, AzureDevOps)

3. Processes – assuming your team has chosen to use GitHub
Everyone: make a GitHub account, and get the education pack at
Everyone (optional): install the Visual Studio plug-in for GitHub at
One person: create the repo, make it private
Everyone: clone the repo
Everyone: work on the project
Create a branch
Add commits locally
Make a pull request
Review of code
Merging the reviewed code into the central branch, called master

5. Terms Repo – the storage place for the project, folders and files
Branch – an alternative copy of the repo; can be changed without changing the master branch
Clone – creates a local copy of a project that already exists
Commit – saves the current state of the branch you are working on (could be the master, but best practice is to work on branches)
Merge – combine branches
Fetch – downloads changes to the repo, but does not integrate them into your working files
Pull – integrates changes with your working files
Push – force out changes made locally to the remote repo(s) (could be used, but pull requests are best practice)
Refer to links on Sprint1 assignment page for reference material on more details

6. End of semester clean-up
If your team’s repo was public, take it down
If you want to host your project, a private repo is recommended
A public repo is ok as long as the final result is the starting point of the repo, if code for previous sprints is public, it can lead to academic misconduct cases (even after graduation)