Skip to content

Commit 0c04cfa

Browse files
authored
remove old bullets
1 parent 4b4ba1b commit 0c04cfa

File tree

1 file changed

+0
-28
lines changed

1 file changed

+0
-28
lines changed

forking_workflow.md

Lines changed: 0 additions & 28 deletions
Original file line numberDiff line numberDiff line change
@@ -74,31 +74,3 @@ Doing so both backs up your changes, and gets you ready to create a pull request
7474
Now, to integrate your changes into the "Parent" repo, you can create a Pull Request via Github.
7575
Navigate to https://github.com/<YOUR_USERNAME>/cnc_github_tutorial.
7676

77-
78-
79-
## 2. Creating a new local branch
80-
One general convention is to keep your local `main` branch tracking the `main` in the remote, and perform any development on a different branch
81-
To do this, run:
82-
```
83-
git checkout -b <SOME_BRANCH_NAME>
84-
```
85-
This will checkout create a new branch, and switch over to that branch. Any changes you make to files now will occur on this new branch, and not affect `main`. Using your favorite text editor, feel free to make any changes to the `test_file.txt` file.
86-
Once saved, we can check the status of our branch using
87-
```
88-
git status
89-
```
90-
and add+commit our changes using:
91-
```
92-
git commit -am "<SOME COMMIT MESSAGE>"
93-
```
94-
95-
## 3. Pushing the branch
96-
Currently your new branch only exists locally and not in the remote repository. To "push" it to the remote repo, run
97-
```
98-
git push origin <YOUR_BRANCH_NAME>
99-
```
100-
This will create a remote branch with the same name, and "push" your changes in your local branch to that remote branch.
101-
102-
## 4. Creating a Pull Request
103-
Your changes are on a branch on remote, but these changes are not integrated into the `main` branch yet. To integrate them, you can issue a "Pull Request", or a "request for someone to pull your changes into `main`"
104-
Github allows you to do this easily through their website.

0 commit comments

Comments
 (0)