Overview, Prereqs, Step 1 & 2 #30
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
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
stephengodderidge
requested changes
Dec 31, 2022
|
|
||
| #### Part 2 (All Team Members) | ||
|
|
||
| 3. Create a feature branch on your local repo |
There was a problem hiding this comment.
minor nit, but if you're breaking into two parts, it'd make sense to start over at "1."
| 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.
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.
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. |
|
You'll also want to rebase onto the latest repo changes, so you don't delete the previous files! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
No description provided.