mirrors
/
rails
mirror of https://github.com/rails/rails
8
0
Fork 0
Code Issues Projects Releases Wiki Activity

Merge pull request #51309 from adityapandit17/update-pull-request-template 

Updated the pull request template, grammatical and general wordings [skip ci]
This commit is contained in:
Guillermo Iguaran 2024-03-15 14:18:06 -07:00 committed by GitHub
parent a534bac9d6 bf48b1515c
commit b3a3c3efea
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
1 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

6
.github/pull_request_template.md vendored
View File

@ -14,7 +14,7 @@ here](https://edgeguides.rubyonrails.org/contributing_to_ruby_on_rails.html#cont
About this template
The following template aims to help contributors write a good description for their pull requests.
We'd like you to provide a description of the changes in your pull request (i.e. bugs fixed or features added), motivation behind the changes, and complete the checklist below before opening a pull request.
We'd like you to provide a description of the changes in your pull request (i.e. bugs fixed or features added), the motivation behind the changes, and complete the checklist below before opening a pull request.
Feel free to discard it if you need to (e.g. when you just fix a typo). -->
@ -33,13 +33,13 @@ This Pull Request changes [REPLACE ME]
### Additional information
<!-- Provide additional information such as benchmarks, reference to other repositories or alternative solutions. -->
<!-- Provide additional information such as benchmarks, references to other repositories, or alternative solutions. -->
### Checklist
Before submitting the PR make sure the following are checked:
* [ ] This Pull Request is related to one change. Changes that are unrelated should be opened in separate PRs.
* [ ] This Pull Request is related to one change. Unrelated changes should be opened in separate PRs.
* [ ] Commit message has a detailed description of what changed and why. If this PR fixes a related issue include it in the commit message. Ex: `[Fix #issue-number]`
* [ ] Tests are added or updated if you fix a bug or add a feature.
* [ ] CHANGELOG files are updated for the changed libraries if there is a behavior change or additional feature. Minor bug fixes and documentation changes should not be included.