-
Notifications
You must be signed in to change notification settings - Fork 43
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
Create pull request template #205
Comments
What are the things we want our contributors to keep in mind when raising PR? Few mandatory items I can think of to be added in every PR
|
@bhavaniravi those are must have, absolutely! At the moment we have a checklist for new features issues. I believe we should have a similar list for pull requests. Not all pull requests will need all the items of the checklist, but they could serve as reminders |
In my opinion, some of the things that we should have:
Only the ones that are applicable for a particular PR should be added. Some Examples of PRs with good descriptions: |
# Description ## What is the current behavior? Currently there is no pull request template so users need to create their own PR descriptions from scratch. This leads to under-descriptive PRs and a lack of consistency. <!-- Issues are required for both bug fixes and features. --> closes: #205 related: ## What is the new behavior? Now when users create a PR, they will get this description automatically to help them fill in relevant details ## Does this introduce a breaking change? No <!-- If this introduces a breaking change, please describe the impact and migration path for existing applications below. --> ### Checklist - [x] Created tests which fail without the change (if possible) - [x] Extended the README / documentation, if necessary closes #205
Context
At the moment the project doesn't have a PR template.
Some examples of PR templates can be seen:
https://github.com/devspace/awesome-github-templates#rocket-templates-for-pull-requests
Acceptance criteria
.github/PULL_REQUEST_TEMPLATE/pull_request_template.md
The text was updated successfully, but these errors were encountered: