Skip to content

Commit

Permalink
Update contribution.md
Browse files Browse the repository at this point in the history
  • Loading branch information
stephanieopala committed Jun 15, 2022
1 parent e19a4d5 commit 4c16112
Showing 1 changed file with 6 additions and 5 deletions.
11 changes: 6 additions & 5 deletions CONTRIBUTING.md
Original file line number Diff line number Diff line change
Expand Up @@ -4,11 +4,12 @@ We are glad to take any and all contributions that will help the community. We h

To better the chances of your Pull request being merged:

- Fork this repository to make your own copy
- Make sure you checkout the `develop` branch `git checkout develop`
- Create your feature branch with the specific issue number( create an issue [HERE](https://github.com/reactdeveloperske/Fantastic-Frontend-React/issues) ): `git checkout -b 254-my-new-learning-resource`
- modify the code with your new resource(s)
- Comment on the issue (if you'd like to be assigned to it) - that way the issue can be assigned to you. OR Create a new issue [here](https://github.com/reactdeveloperske/Fantastic-Frontend-React/issues).
- Fork this repository to make your own copy.
- Create your feature branch with the specific issue number `git checkout -b 254-my-new-learning-resource`
- Modify the code with your new resource(s)
- Commit your changes: `git commit -m 'Add some feature'`
- Push to the created branch: `git push origin 254-my-new-learning-resource`
- Submit a pull request.
- Submit a pull request. In your pull request description, reference the issue it resolves (see [linking a pull request to an issue using a keyword](https://docs.github.com/en/free-pro-team@latest/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))
- ex. `Updates out of date content [Fixes #1234]`
- Sit back, and wait for a review and a merge :tada:

0 comments on commit 4c16112

Please sign in to comment.