IntenseWebs/grafana
3
0
Fork 0
mirror of https://github.com/grafana/grafana.git synced 2024-12-01 13:09:22 -06:00
Code Issues Packages Projects Releases Wiki Activity
b26ef1db25
grafana/.github/PULL_REQUEST_TEMPLATE.md

35 lines
1.2 KiB
Markdown
Raw Normal View History

GitHub Templates: Pull Request Template update (#18300) * Imperative mood The English language suggests that when giving out instructions or considerations is best to use imperative mood as the writing style. Done as part of this commit: - some worth smithing to match this style - changed the format to match the fact that this is commonly read as part of a text box when opening up your PRs - and extended a few descriptions to make it more friendly for newcomers
2019-07-31 05:29:57 -05:00
<!--
Thank you for sending a pull request! Here are some tips:
1. If this is your first time, please read our contribution guide at https://github.com/grafana/grafana/blob/master/CONTRIBUTING.md
2. Ensure you include and run the appropriate tests as part of your Pull Request.
3. In a new feature or configuration option, an update to the documentation is necessary. Everything related to the documentation is under the docs folder in the root of the repository.
4. If the Pull Request is a work in progress, make use of GitHub's "Draft PR" feature and mark it as such.
5. If you can not merge your Pull Request due to a merge conflict, Rebase it. This gets it in sync with the master branch.
6. Name your PR as "<FeatureArea>: Describe your change", e.g. Alerting: Prevent race condition. If it's a fix or feature relevant for the changelog describe the user impact in the title. The PR title is used to auto-generate the changelog for issues marked with the "add to changelog" label.
Updated pull request rtemplate
2019-03-07 04:41:07 -06:00
-->
**What this PR does / why we need it**:
**Which issue(s) this PR fixes**:
GitHub Templates: Pull Request Template update (#18300) * Imperative mood The English language suggests that when giving out instructions or considerations is best to use imperative mood as the writing style. Done as part of this commit: - some worth smithing to match this style - changed the format to match the fact that this is commonly read as part of a text box when opening up your PRs - and extended a few descriptions to make it more friendly for newcomers
2019-07-31 05:29:57 -05:00
Updated pull request rtemplate
2019-03-07 04:41:07 -06:00
<!--
GitHub Templates: Pull Request Template update (#18300) * Imperative mood The English language suggests that when giving out instructions or considerations is best to use imperative mood as the writing style. Done as part of this commit: - some worth smithing to match this style - changed the format to match the fact that this is commonly read as part of a text box when opening up your PRs - and extended a few descriptions to make it more friendly for newcomers
2019-07-31 05:29:57 -05:00
* Automatically closes linked issue when the Pull Request is merged.
Usage: "Fixes #<issue number>", or "Fixes (paste link of issue)"
Updated pull request rtemplate
2019-03-07 04:41:07 -06:00
-->
GitHub Templates: Pull Request Template update (#18300) * Imperative mood The English language suggests that when giving out instructions or considerations is best to use imperative mood as the writing style. Done as part of this commit: - some worth smithing to match this style - changed the format to match the fact that this is commonly read as part of a text box when opening up your PRs - and extended a few descriptions to make it more friendly for newcomers
2019-07-31 05:29:57 -05:00
Updated pull request rtemplate
2019-03-07 04:41:07 -06:00
Fixes #
**Special notes for your reviewer**:
Reference in New Issue Copy Permalink