-
Notifications
You must be signed in to change notification settings - Fork 21
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
Use issue templates #251
Use issue templates #251
Conversation
This is so I don't have to keep asking the same set of questions when helping people troubleshoot or consider new features/ideas
instead provide another avenue for feedback
I'm first testing these changes in the test repo. It is not working as expected... |
Ok I've got it working the way I wanted. you can test it out in the test repo by opening a new issue |
it might be good to add the following to
|
contact_links: | ||
- name: cpp-linter discussions | ||
url: https://github.com/orgs/cpp-linter/discussions | ||
about: A place for feedback not specific to cpp-linter-action |
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.
about: A place for feedback not specific to cpp-linter-action | |
about: A place for feedback not specific to cpp-linter-action | |
- name: "(maintainers only) Blank issue" | |
url: https://github.com/cpp-linter/cpp-linter-action/issues/new | |
about: For maintainers only. |
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.
That link will only direct you to the offerings of templates. What you want would basically change line at the beginning of this file:
blank-issues-enabled: true
We could do that provisionally. But if users end up not using the templates for reporting problems or suggesting new features, then I'll have to insist on disabling blank issues.
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 could also add a more general template for questions. That way us maintainers can "abuse" the question template like a blank issue template.
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.
I added a blank template called "Maintainers' note". This way it should be clear that end-users should reconsider before using it to report a bug or request a feature.
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, we should not set blank-issues-enabled: true
which will allow users to have permission to open a blank issue.
https://github.com/cpp-linter/cpp-linter-action/issues/new is a link that should only the maintainer have permission to open a blank issue, this is how I saw it done from pip project https://github.com/pypa/pip/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.
I didn't know account permission had any effect. With that knowledge, we can certainly do that.
This is so I don't have to keep asking the same set of questions when helping people troubleshoot or consider new features/ideas
Tip
See github tutorial
also yaml schema for github forms