summaryrefslogtreecommitdiffstats
path: root/.github/ISSUE_TEMPLATE (follow)
Commit message (Collapse)AuthorAgeFilesLines
* Unify additional info + WYSIWYG as optional input in the documentation ↵Sviatoslav Sydorenko2021-03-091-10/+4
| | | | report issue form (#73796)
* feature_request: Component Name (#73787)John R Barker2021-03-041-1/+1
| | | Typo in name results in Bot shouting
* Convert markdown issue templates into issue forms (#73751)Sviatoslav Sydorenko2021-03-037-118/+291
| | | | | | | | | | | | | * 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>
* Update config.yml (#70154)John R Barker2020-06-231-2/+2
| | | | | | typos & branding * Update .github/ISSUE_TEMPLATE/config.yml Co-authored-by: Rick Elrod <rick@elrod.me>
* Add external refs to the GH issue template chooser (#66743)Sviatoslav Sydorenko2020-01-242-8/+26
| | | | | | | | This change replaces a dummy template for security issues with a proper reference to the doc. It also adds pointers to a few other useful community pages. Ref: https://help.github.com/en/github/building-a-strong-community/configuring-issue-templates-for-your-repository#configuring-the-template-chooser
* Revert "Use GitHub Issue Templates to assign labels (#53356)" (#53419)Matt Martz2019-03-063-3/+0
| | | This reverts commit 44b347aef515c7da225ec905380c936efe4d0bb6.
* Use GitHub Issue Templates to assign labels (#53356)John R Barker2019-03-053-0/+3
|
* Remove DEPENDENCY PROBLEMS from bug_report ISSUE TEMPLATE (#52248)Adam Miller2019-02-191-14/+0
| | | | | | | | 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>
* Improve the issue template for dependency problems (#51657)Will Thames2019-02-061-0/+15
| | | | | | | 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
* readded rstBrian Coca2018-12-111-1/+1
|
* added missing guessBrian Coca2018-12-111-1/+1
|
* Let submitters know component is 'best effort' (#49619)Brian Coca2018-12-113-3/+3
| | | | | | * Let submitters know component is 'best effort' * updated as per FB
* Improve GitHub templates (#44455)Dag Wieers2018-09-043-112/+45
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | * 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 (#43836)Eric Brown2018-08-091-0/+8
| | | | | | | | * 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
* Move summary to top for issue template (#40401)Sam Doran2018-05-213-9/+9
|
* Add emojii to issue template titlesSviatoslav Sydorenko2018-05-073-3/+3
| | | | According to https://gitmoji.carloscuesta.me/
* Integrate bug/docs report and FR issue templatesSviatoslav Sydorenko2018-05-073-0/+183