-
Notifications
You must be signed in to change notification settings - Fork 1.2k
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
#11567 Add templates for new issues. #11588
Conversation
I think that this is ready for an initial review needs-review |
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.
Looks like a great start, some suggestions inline.
**Testing environment** | ||
- OS: [e.g. linux, windows, macos] | ||
- Twisted version [e.g. 22.2.0] | ||
- Reactor [e.g. select, iocp] |
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.
See the feedback on the regular-bug template.
Co-authored-by: Glyph <glyph@twistedmatrix.com>
Thanks for the review. I have applied the suggestions and triggered the auto-merge. I think that is important to have the templates first, so that we can interact with them. |
Scope
Fixes #11567
This is the initial suggestion for some templates.
They are simple text templates.
Changes
The following templates were created with the following tags auto applied:
bug
bug
andrelease-blocker
documentation
Web forms are not yet used - release-blocker
How to test
There is no way for end to end testing until this is merged,
So maybe make sure this looks ok in general, merge it and then after a hands-on testing, we can update what is left in a separate PR.
With these changes, when a new report is made, users must select one of the available options.
The option of a blank issue is disabled.