| ... | ... | @@ -2621,9 +2621,31 @@ Now it is time to push all of our work. |
|
|
|
2. Open the web version of your repo (e.g., your exiting Github repo or
|
|
|
|
GitLab repo) and examine the results.
|
|
|
|
3. If you would like an existing example... navigate to <https://git-community.cs.odu.edu/tkennedy/git-workshop>.
|
|
|
|
4. Make a change to `README.md` through the web interface.
|
|
|
|
5. Go back to your terminal.
|
|
|
|
6. Run `git pull`
|
|
|
|
|
|
|
|
You should now see the changes to `README.md` in your local copy of the file.
|
|
|
|
|
|
|
|
|
|
|
|
# Cloning an Existing Repository
|
|
|
|
|
|
|
|
Cloning a git repo is far less work than seeting one up locally (from scratch).
|
|
|
|
|
|
|
|
1. Find the URL of a repo you want to clone (and for which you have edit
|
|
|
|
privileges).
|
|
|
|
2. Make sure you have `cd`-ed out of any existing repos.
|
|
|
|
3. Run `git clone REPO_URL`
|
|
|
|
|
|
|
|
You now have a local copy of the repo. You can `push`, `pull`, examine and edit
|
|
|
|
the repo using the commands we have discussed.
|
|
|
|
|
|
|
|
|
|
|
|
# Future Work
|
|
|
|
|
|
|
|
If time permits we will discuss:
|
|
|
|
|
|
|
|
- `git merge`
|
|
|
|
- `git blame`
|
|
|
|
- git aliases
|
|
|
|
|
