What if we tracked our file with a better names for each version?
We will call the descriptions in bold commit messages.
Commit often but not too often. If in doubt, commit often.
It seems like you (I did too) wrote an R code which includes randomness but for which we forgot to set seed. Let’s correct the error while also version controlling using the repo 01-intro-github-username
.
Important task for now is to first commit and then push.
repo is a short form of repository. Repositories contain all of your project’s files as well as each file’s revision history.
For this workshop our repos are hosted on Github.
To clone a GitHub repo to our computer, we first copy the cloning link as shown in screencast then start an RStudio project using that link.
Cloning a repo pulls (downloads) all the elements of a repo available at that specific time.
Once you make changes to your repo, you can take a snapshot of your changes with a commit.
This way if you ever have to go back in version history you have your older commits to get back to. This is especially useful, for instance, if you want to go back to an earlier solution you have committed.
All the commits you make will initially be local (i.e. on your own computer).
In order for me to see your commits, you have to push your commits. In other words upload your files at the stage in that specific time.
Git: is software for tracking changes in any set of files
GitHub: is an internet host for Git projects.
repo: is a short form of repository. Repositories contain all of your project’s files as well as each file’s revision history.
clone: Cloning a repo pulls (downloads) all the elements of a repo available at that specific time.
commit: A snapshot of your repo at a specific point in time. We distinguish each commit with a commit message.
push: Uploads the latest “committed” state of your repo to GitHub.