Open Github Desktop, open the Preferences menu, then sign in with your Github Account.
Keeping (g)it simple
Git and github are comprehensive tools for version control, and can become rather complicated.
We will keep things simple and use point and click tools from Github Desktop (and the Github website)
Alternatively, git and github can be controlled from the command line (e.g., unix terminal, not covered in this tutorial)
Next, a quick conceptual overview
Normal folders and git folders
Git folders look like normal folders, but have hidden .git files
git folders
Git Folders store history of changes (version control)
git master and branches
Can have multiple branches
usually for development purposes
git basics
Make changes to files
“Commit” the changes
git updates current version
and saves the previous version
git + github
copy from local to Github.com
“push” to Github.com
“pull/sync” from Github.com
Looks complicated, but…
Complicated at first but…
Relatively easy with Github Desktop
Similar to Dropbox, but with commit notes
let’s get to some examples…
Create a new git folder from RStudio
Add new repo to Githup Desktop
Github Desktop (view and manage your repos)
Commit then publish
Publishing to Github.com
Viewing your repo on Github.com
Work on your files
Commit new changes in Github Desktop
Publish them to Github (if you want to)
Changes appear on Github.com
That’s Github in a nutshell
Before moving on the next module…
A few more tips
Making new local repos
“Create new repository” from Github Desktop
Creates a new git-ready folder
It is only local to your computer, unless you choose to publish it
It will be added to list of repositories in Github Desktop
Cloning and Forking
From Github.com, if you have a Github account
Cloning
You can “clone” anyone else’s public repository on Github.com
This is like downloading as a .zip, but the repo will be downloaded and appear in Github Desktop on your local file system
Forking
press the fork button on Github.com
copies the repo to your Github.com account (in the cloud)
forked copies are connected to the original repo
If you make changes, you can make “pull” requests to have your changes merged with the original repo
Github Issues
Normally used to report and address “bugs” in software, but can be used as useful way to have discussions (with collaborators or yourself) about project-related tasks:
Can “open” specific issues
creates a discussion thread for the issu
Can “close” issues
once the issue has been addressed
All threaded discussions are preserved, useful as a record of project development
