* Convert markdown issue templates into issue forms
* Limit allowed issues to the form based ones
* Title-case the form field labels
Co-authored-by: John R Barker <john@johnrbarker.com>
* Remove CoC checkboxes from the forms
Co-authored-by: John R Barker <john@johnrbarker.com>
As per Community Core Meeting 2019-02-14 consensus, remove this
section of the bug report issue template.
https://github.com/ansible/community/issues/436
Signed-off-by: Adam Miller <admiller@redhat.com>
So many reports of missing modules could be solved
more quickly with the info from `python_requirements_facts`
Replace the legacy issue template with a link to the
new interface
* Improve GitHub templates
The existing templates are basically a copy for each type of issue (bug,
feature, doc) whereas we can make the template more specific to the task
at hand.
This PR includes:
- More specific sections depending on the type of issue
- More concise and direct instructions (NO NEED FOR FRUSTRATION CAPS!)
- Single-line comments (no need to guide people to avoid wrong edits)
- Improved paste area
- Better headings/titles
- No 'Summary' title for PRs (so commit information is placed correctly)
This PR would require some improvements to Ansibot.
* Remove controversial Ansibot stuff
Make it easier to get the first batch merged.
* Restore ISSUE_TEMPLATE.md
* Incorporate reviewer suggestions
* Make OS / ENVIRONMENT doc-related
* Rephrase Ansibot-related message
* Create a template for security related bugs
This template serves as a redirect for people who might not know where to open security related issues. It guides them to email security@ansible.com instead of opening an issue here.
* Update security_bug_report.md
