forked from ManageIQ/manageiq
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge pull request ManageIQ#11159 from Fryguy/update_pull_request_tem…
…plate Update PR template with some styling changes
- Loading branch information
Showing
1 changed file
with
11 additions
and
15 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,19 +1,15 @@ | ||
Purpose or Intent | ||
----------------- | ||
> Describe the rationale and use case for this pull request. Provide any background, examples, and images that provide further information to accurately describe what it is that you are adding to the repo. Add subsections as necessary to organize and feel free to link and reference other PRs as necessary, but also include them in the links section below as a quick reference. | ||
> | ||
> Guidelines: | ||
> * Keep Pull Request titles short and to the point, ideally under 72 characters | ||
> * Provide as much context/info in the description as necessary to get the reviewer up to the same domain knowledge level as yourself | ||
> * Keep code changes as short and implementing a single feature/bug fix/refactoring when possible | ||
Describe the rationale and use case for this pull request. Provide any background, examples, and images that provide further information to accurately describe what it is that you are adding to the repo. Add subsections as necessary to organize and feel free to link and reference other PRs as necessary, but also include them in the links section below as a quick reference. | ||
|
||
Guidelines: | ||
* Keep Pull Request titles short and to the point, ideally under 72 characters | ||
* Provide as much context/info in the description as necessary to get the reviewer up to the same domain knowledge level as yourself | ||
* Keep code changes as short as possible and implementing a single feature/fix/refactoring, when possible | ||
|
||
Links | ||
----- | ||
> * http://documentation.for/library/that/I/am/adding | ||
> * [PR relevant issue or pull_request](#123) | ||
## Links [Optional] | ||
|
||
* http://documentation.for/library/that/I/am/adding | ||
* [PR relevant issue or pull_request](#123) | ||
|
||
Steps for Testing/QA | ||
-------------------- | ||
> [Optional] If there are any manual steps that you would like the reviewer(s) to take to verify your changes, please describe in detail the steps to reproduce the features added by the pull request, or the bug before and after the change. | ||
## Steps for Testing/QA [Optional] | ||
|
||
If there are any manual steps that you would like the reviewer(s) to take to verify your changes, please describe in detail the steps to reproduce the features added by the pull request, or the bug before and after the change. |