New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Adds a PR template #2764
Adds a PR template #2764
Conversation
.github/pull_request_template.md
Outdated
|
||
- [ ] Link to the related issue with requirements and/or clearly describe 1) what problem this solves and 2) the requirements to review it against. | ||
- [ ] Update the `CHANGELOG.md` file with the added feature or fix. If there is not yet a heading for an upcoming release, add one following the established pattern. | ||
- [ ] Keep the pull request minimal! Break large updates into separate pull requests whenever possible. Small requests get reviewed more quickly. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
As long as they make sense independently and can be tested independently.
- [ ] Link to the related issue with requirements and/or clearly describe 1) what problem this solves and 2) the requirements to review it against. | ||
- [ ] Update the `CHANGELOG.md` file with the added feature or fix. If there is not yet a heading for an upcoming release, add one following the established pattern. | ||
- [ ] Keep the pull request minimal! Break large updates into separate pull requests whenever possible. Small requests get reviewed more quickly. | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- Follow our style guide. Most modules have an eslint configuration, so you can run
npx eslint .
in the module if your editor does not automatically pick up on that.
@@ -2,6 +2,7 @@ Please ensure your pull request follows these guidelines: | |||
|
|||
- [ ] Link to the related issue with requirements and/or clearly describe 1) what problem this solves and 2) the requirements to review it against. | |||
- [ ] Update the `CHANGELOG.md` file with the added feature or fix. If there is not yet a heading for an upcoming release, add one following the established pattern. | |||
- [ ] Keep the pull request minimal! Break large updates into separate pull requests whenever possible. Small requests get reviewed more quickly. | |||
- [ ] Keep the pull request minimal! Break large updates into separate pull requests for individual features/fixes whenever possible. Small requests get reviewed more quickly. | |||
- [ ] All tests must pass, including the linters. Run `npm run lint` to test code linting independently. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
If the module does not yet have a lint
task please adhere to the formatting style in place.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@boutell This is a template only for core, which has the linter test.
PR template meant primarily to help us remember to update the changelog and keep changes manageable.