jprdonnelly/freeCodeCamp
1
0
Fork 0
mirror of https://github.com/freeCodeCamp/freeCodeCamp.git synced 2026-01-05 21:03:24 -05:00
Code Issues Projects Releases Wiki Activity

doc: change wording of PR guidance (#47070)

Browse Source 
* TYPO: improved words

* Update docs/how-to-open-a-pull-request.md

Co-authored-by: Muhammed Mustafa <muhammed@freecodecamp.org>

* Update docs/how-to-open-a-pull-request.md

Co-authored-by: Muhammed Mustafa <muhammed@freecodecamp.org>

* Update docs/how-to-open-a-pull-request.md

Co-authored-by: Muhammed Mustafa <muhammed@freecodecamp.org>

* Update docs/how-to-open-a-pull-request.md

Co-authored-by: Jeremy L Thompson <jeremy@jeremylt.org>

* Update docs/how-to-open-a-pull-request.md

Co-authored-by: Jeremy L Thompson <jeremy@jeremylt.org>

Co-authored-by: Muhammed Mustafa <muhammed@freecodecamp.org>
Co-authored-by: Jeremy L Thompson <jeremy@jeremylt.org>
This commit is contained in:
kartik
2022-07-30 01:14:32 +05:30
committed by GitHub
parent cd4d51b5a9
commit 82691be5e2
1 changed files with 3 additions and 3 deletions
Download Patch File Download Diff File Expand all files Collapse all files

6
docs/how-to-open-a-pull-request.md
View File

@@ -15,7 +15,7 @@ We recommend using [conventional title and messages](https://www.conventionalcom
>
> `fix(learn): tests for the do...while loop challenge`
When opening a Pull Request(PR), you can use the below to determine the type, scope (optional), and description.
Whenever you open a Pull Request(PR), you can use the below to determine the type, scope (optional), and description.
**Type:**
@@ -32,7 +32,7 @@ You can select a scope from [this list of labels](https://github.com/freeCodeCam
**Description:**
Keep it short (less than 30 characters) and simple, you can add more information in the PR description box and comments.
Keep it short (less than 30 characters) and simple; you can add more information in the PR description box and comments.
Some examples of good PR titles would be:
@@ -55,7 +55,7 @@ Some examples of good PR titles would be:
3. Submit the pull request from your branch to freeCodeCamp's `main` branch.
4. In the body of your PR include a more detailed summary of the changes you made and why.
4. Include a more detailed summary of the changes you made and how your changes are helpful in the body of your PR.
- You will be presented with a pull request template. This is a checklist that you should have followed before opening the pull request.