Add contributing md 120 - #126
Conversation
|
@chelseybeck @nyarly Please take a look at it, and make any suggestions for revision. Thank you |
|
|
||
| ### **Working on an issue** | ||
|
|
||
| For each issue you address, create a new branch. Working on topic branches ensures that your main branch(named `master`)remains untouched and makes it easier to synchronize your fork with the main project. |
There was a problem hiding this comment.
| For each issue you address, create a new branch. Working on topic branches ensures that your main branch(named `master`)remains untouched and makes it easier to synchronize your fork with the main project. | |
| For each issue you address, create a new branch. Working on topic branches ensures that your main branch(named `main`)remains untouched and makes it easier to synchronize your fork with the main project. |
|
|
||
| For each issue you address, create a new branch. Working on topic branches ensures that your main branch(named `master`)remains untouched and makes it easier to synchronize your fork with the main project. | ||
|
|
||
| #### **Working on an issue (1): Verify current branch is `master`** |
There was a problem hiding this comment.
| #### **Working on an issue (1): Verify current branch is `master`** | |
| #### **Working on an issue (1): Verify current branch is `main`** |
|
|
||
| #### **Working on an issue (1): Verify current branch is `master`** | ||
|
|
||
| first make sure you are on the master branch. |
There was a problem hiding this comment.
| first make sure you are on the master branch. | |
| first make sure you are on the main branch. |
| first make sure you are on the master branch. | ||
|
|
||
| ```bash | ||
| git checkout master |
There was a problem hiding this comment.
| git checkout master | |
| git checkout main |
| git checkout master | ||
| ``` | ||
|
|
||
| Update your master branch with the latest changes |
There was a problem hiding this comment.
| Update your master branch with the latest changes | |
| Update your main branch with the latest changes |
| Update your master branch with the latest changes | ||
|
|
||
| ``` | ||
| git pull upstream master |
There was a problem hiding this comment.
| git pull upstream master | |
| git pull upstream main |
| After committing your changes locally, you can use below commands to push your committed changes to a remote repository, making them accessible to others working on the same projects. | ||
|
|
||
| ```bash | ||
| git push --set-upstream add-contributing-md-120 |
There was a problem hiding this comment.
| git push --set-upstream add-contributing-md-120 | |
| git push --set-upstream origin add-contributing-md-120 |
|
@awlFCCamp I recommended a few changes. GitHub used to default to naming branches 'master', but switched to 'main'. Newer repos (like ours) use 'main'. Other than that, this looks great! Thanks for working on it 😄 |
|
@chelseybeck I made changes. Please take a look at it, and make any suggestions for revision. Thank you. |
abbyz123
left a comment
There was a problem hiding this comment.
Looks good to me. Thank you so much for your work!
Fixes #120
Added a contributing markdown file to provide clear instructions for new contributors. Added instructions for making contributions to the repo: forking repo, cloning repo, creating a new branch, adding committing, pushing changes, and creating a pull request.