Include repo name in issue template component dropdown
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 0
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
Extracted from a side comment on #5
having to select "Product or component" made me wonder where the issue would end up
While filing an issue in a hexpm-owned repo I thought there was some automation in place to auto-route issues from one repo to another. After looking at the diff of #4, I'm tempted to believe there is not, and the selection is only informational.
From the perspective of filing new issues, I found that experience off putting, too many form fields to go through.
If that is genuinely helping maintainers with the routing, then my suggestion is to include the intended repos next to each component.
Example
options:
- Hex.pm website or API (hexpm/hexpm)
- Hex CLI (hexpm/hex)
Affected dropdowns
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Review the affected dropdowns in .github/ISSUE_TEMPLATE/bug_report.yml, documentation.yml, feature_request.yml, and question.yml, using the linked sections as the starting point. Update each component option to include its intended repository name, then verify that all four templates present the routing information consistently.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Clearly specified
- Newbie friendliness
- 88/100