mirror of
https://github.com/ansible-collections/community.general.git
synced 2024-09-14 20:13:21 +02:00
43ba8813d3
If a user makes a PR with a single, detailed commit message, github will put that at the top of the PR. Move our summary field to the top of the PR template so that it is next to where the commit message is placed. Users can then easily merge the two together or supplement the commit message with additional information that we ask for.
37 lines
910 B
Markdown
37 lines
910 B
Markdown
##### SUMMARY
|
|
<!--- Describe the change, including rationale and design decisions -->
|
|
|
|
<!---
|
|
If you are fixing an existing issue, please include "Fixes #nnn" in your
|
|
commit message and your description; but you should still explain what
|
|
the change does.
|
|
-->
|
|
|
|
##### ISSUE TYPE
|
|
<!--- Pick one below and delete the rest: -->
|
|
- Feature Pull Request
|
|
- New Module Pull Request
|
|
- Bugfix Pull Request
|
|
- Docs Pull Request
|
|
|
|
##### COMPONENT NAME
|
|
<!--- Name of the module/plugin/module/task -->
|
|
|
|
##### ANSIBLE VERSION
|
|
<!--- Paste verbatim output from “ansible --version” between quotes below -->
|
|
```
|
|
|
|
```
|
|
|
|
|
|
##### ADDITIONAL INFORMATION
|
|
<!---
|
|
Include additional information to help people understand the change here.
|
|
For bugs that don't have a linked bug report, a step-by-step reproduction
|
|
of the problem is helpful.
|
|
-->
|
|
|
|
<!--- Paste verbatim command output below, e.g. before and after your change -->
|
|
```
|
|
|
|
```
|