-
Notifications
You must be signed in to change notification settings - Fork 369
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Overview, Prereqs, Step 1 & 2 #30
base: master
Are you sure you want to change the base?
Overview, Prereqs, Step 1 & 2 #30
Conversation
Cleaning up and changing content for more collaborative class material
Adding more changes to the group assignment
Adding a note about the folder that currently exists
2. Give edit permissions to your team | ||
|
||
#### Part 2 (All Team Members) | ||
|
||
3. Create a feature branch on your local repo |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
minor nit, but if you're breaking into two parts, it'd make sense to start over at "1."
|
||
> Repository (Repo): A folder that holds your code. This folder is special because it has a hidden `.git` folder that holds information about how your repository has changed over time. | ||
|
||
Instead of adding your changes directly to someone else's repo, you can create a copy of their repository to work with. When you create this copy, we call it "forking the repository." | ||
|
||
Conceptually, think about hitting a fork in the road -- the road splits into two. This is the same with forking in git. Forking simply creates a snapshot of the base repository (`stephengodderidge/learn-git`) that you have permission to make changes to. | ||
Conceptually, think about hitting a fork in the road -- the road splits into two. This is the same with forking in git. Forking simply creates a snapshot of the base repository (`chingtong/learn-git`) that you have permission to make changes to. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I don't think these references to the fork should be included in the original
1. Make sure you're on the base page of the `learn-git` repository: [https://github.comstephengodderidge/learn-git](https://github.com/stephengodderidge/learn-git). | ||
2. In the top right-hand corner, you'll see a button that says "Fork". Click it. | ||
You'll see a screen that shows "Forking repository". You'll now find yourself on a new repo page. If you look in the top left, you'll see that this repo is based on your `<your-github-username/learn-git>`. | ||
1. Make sure you're on the base page of the `learn-git` repository: [https://github.com/chingtong/learn-git](https://github.com/chingtong/learn-git). |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same thing here -- remove the updated link
1. Make sure you're on the base page of the `learn-git` repository: [https://github.com/chingtong/learn-git](https://github.com/chingtong/learn-git). | ||
2. In the top right-hand corner, you'll see a button that says `Fork`. Click it. You'll see a screen that shows "Forking repository". You'll now find yourself on a new repo page. If you look in the top left, you'll see that this repo is based on your `<your-github-username/learn-git>`. | ||
|
||
Congrats! You've created a fork! This is simply a copy of the base repository `chingtong/learn-git`. We will use this new repository as a place for your team can share code. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
same here
You'll also want to rebase onto the latest repo changes, so you don't delete the previous files! |
No description provided.