Skip to content

fork_clone_sync.md

Latest commit

 

History

History
46 lines (29 loc) · 2.1 KB

fork_clone_sync.md

File metadata and controls

46 lines (29 loc) · 2.1 KB

FORKING, CLONING, & SYNCING

HOW TO FORK AND CLONE

CREATE YOUR OWN COPY

  1. FORK it to your own GitHub account
  2. COPY the link from your new repo on GitHub
  3. CLONE it to your local machine. Example:

git clone https://github.com/[YourUsername]/[name-of-git-repository]

PRACTICE IN YOUR OWN BRANCHES

If you want to update your forked repository from my parent repository when I add or change things to mine in the future, there are instructions below this section. It will go much easier if you don't ever change the code in main. Instead, do the following:

  1. From main, use the command git checkout -b new-branch-name to create your own branch for practicing (example: functions-practice).
  2. Practice as much as you'd like in your new branch, making commits as you add code.
  3. When you are ready to work on something different in another new branch, use the command git checkout main to return to main and then you can repeat the two steps above.

HOW TO SYNC YOUR REPO WITH MINE AFTER I MAKE UPDATES

Set the upstream link:

  1. On your local machine, make sure you are in the correct directory in the terminal.
  2. Use the command git remote add upstream https://github.com/CodeWithCarrie/[name-of-git-repository]

You now have a direct link to my original repo!

Use the command git remote -v to verify that you have linked to both origin (your forked repo) and upstream (my original repo)

Update your repo anytime I make changes in the future:

  1. On your local machine, make sure you are in the correct directory in the terminal.
  2. If you have any uncommitted changes, stage and commit them.
  3. Make sure you are in the branch you wish to update (e.g. main)
  4. Use the command git fetch upstream so your local repo has knowledge of changes I made in my repo
  5. Use the command git rebase upstream/main to sync your repo

Check to see which branches you already have:

  1. You can use the command git branch anytime to see what local branches you have
  2. The command git branch -r will show you branches that exist on GitHub (after you've fetched that knowledge)