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.
* Try to avoid module-related tickets in the core Ansible project
Since most users still report module-related problems in the Ansible core GitHub project, I added a warning at the top of the template.
Maybe it could help if the various projects would have more specific names ?
- ansible/ansible -> ansible/main (or something even better ?)
- ansible/ansible-modules-core -> ansible/modules-core
- ansible/ansible-modules-extras -> ansible/modules-extras
I am sure someone can come up with perfect names ;-)
* Remove 'module' from the component options
I would prefer to again note that modules should go elsewhere, but don't want to bloat the text too much.
- Instruct to verify if an issue/request already exists
- Use uppercase for titles (easier to parse as titles)
- Remove empty lines where it makes sense (instructions)
- Ensure that commit-message appears directly under summary (pull-requests)
In essence, most people do not need to use the templates directly,
getting them out of the way increases the signal-to-noise ratio of
the root directory. Direct people to what they are looking for.
