feat: Issue Template #527
feat: Issue Template #527
Conversation
|
@choir27 is attempting to deploy a commit to the Pieces for Developers Team on Vercel. A member of the Team first needs to authorize it. |
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
.github/ISSUE_TEMPLATE/bug.yml
Outdated
| description: What software are you referring to? | ||
| multiple: true | ||
| options: | ||
| - Desktop Application |
There was a problem hiding this comment.
We should probably add the other extensions like Sublime / Raycast.
There was a problem hiding this comment.
I added the other extensions, can you double-check if I missed anything/should remove anything?
There was a problem hiding this comment.
This is not the repo where bug reports should be. That is why we have the link to our support repo in the config file.
So we don't need this bug report. We only need 1 general issue template and then we can keep the config file where people can go to report bugs or feature requests
| contact_links: | ||
| - name: Feature or Enhancement Request | ||
| url: https://github.com/pieces-app/support/discussions | ||
| about: Post your idea in discussions for the Pieces team and community to discuss! No newline at end of file |
There was a problem hiding this comment.
I want to keep this config file so that people can still go to our support repo for product feature requests.
You can change the blank_issues_enabled boolean to false though since we won't need it
There was a problem hiding this comment.
Also, we should add to the - name: so that it includes feature/enhancement requests as well as bug reports
.github/ISSUE_TEMPLATE/bug.yml
Outdated
| description: What software are you referring to? | ||
| multiple: true | ||
| options: | ||
| - Desktop Application |
There was a problem hiding this comment.
This is not the repo where bug reports should be. That is why we have the link to our support repo in the config file.
So we don't need this bug report. We only need 1 general issue template and then we can keep the config file where people can go to report bugs or feature requests
| A clear and concise description of any alternative solutions or features you've considered. | ||
|
|
||
| **Additional context** | ||
| Add any other context or screenshots about the feature request here. No newline at end of file |
There was a problem hiding this comment.
So this could become the only issue template that we actually use. Im not sure if Feature Request is the best name for this though
There was a problem hiding this comment.
Changed the name to Enhancement, lmk what you think
…es, replace feature request for enhancement and update content accordingly
3 participants
Add bug report issue and feature request to maintain consistency across created issues
Feature request referenced from:
https://github.com/pieces-app/markdown_widget/blob/master/.github/ISSUE_TEMPLATE/feature_request.md?plain=1
Bug report referenced from:
https://github.com/pieces-app/support/blob/main/.github/ISSUE_TEMPLATE/bug.yml