-
Notifications
You must be signed in to change notification settings - Fork 24k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Convert markdown issue templates into issue forms #73751
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
We should probably experiment with this in a separate repo so everyone can see how it will work. That will make it easier to comment on and decide if this is something we want.
Also, the checkboxes should be omitted. They aren't part of the original templates.
65f4344
to
7a318ee
Compare
7a318ee
to
c6a6d57
Compare
c6a6d57
to
e510489
Compare
- type: checkboxes | ||
attributes: | ||
label: Code of Conduct | ||
description: | | ||
Read the [Ansible Code of Conduct][CoC] first. | ||
|
||
[CoC]: https://docs.ansible.com/ansible/latest/community/code_of_conduct.html?utm_medium=github&utm_source=issue_form--documentation_report.yml | ||
options: | ||
- label: I agree to follow the Ansible Code of Conduct | ||
required: true |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@mattclay are you talking about this ☝️? Would it be better to add it in a separate PR or are you opposed to the idea in general?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes, it's not part of the current templates.
I wouldn't open a separate PR to add it either. The issue templates should contain the minimum text and prompts necessary to facilitate reporting issues. We should review them periodically to see if there is anything we can remove or clarify to encourage better issue reporting. For example:
- The documentation issue probably doesn't need the "OS / Environment" section. I believe @bcoca already mentioned this elsewhere.
- With the way these templates work, the "Additional Information" section is redundant with the comment section that immediately follows.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
- With the way these templates work, the "Additional Information" section is redundant with the comment section that immediately follows.
WSYWIG is only enabled for one form, for screenshots. It's non-enforceable.
I wouldn't open a separate PR to add it either.
I checked with @gundalow if it's a good idea to have the CoC check and he thinks it is.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you for doing this.
Co-authored-by: John R Barker <john@johnrbarker.com>
@mattclay I've made a demo in a separate repo as you suggested: /~https://github.com/ansible/issue-forms-demo-for-ansible/issues/new/choose |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
This is great, thank you for doing it.
SUMMARY
This change makes the submitted GitHub issue structure predictable.
👉 ISSUE FORMS FROM THIS PR IN THE DEMO REPOSITORY 👈
UPD: @mkrizek verified that ansibull is capable of digesting issues created with these forms.
ISSUE TYPE
COMPONENT NAME
.github/ISSUE_TEMPLATE/*
ADDITIONAL INFORMATION
https://gh-community.github.io/issue-template-feedback/structured/