Add issue forms for tool requests and bugs, with tool-type auto-labeling - #64
Open
udid-aws wants to merge 2 commits into
Open
Add issue forms for tool requests and bugs, with tool-type auto-labeling#64udid-aws wants to merge 2 commits into
udid-aws wants to merge 2 commits into
Conversation
- community-request.yml: roadmap intake form (applies 'request' label) - bug-report.yml: bug form (applies 'bug' label), kept off the roadmap - config.yml: contact links, blank issues enabled - label-tool-type.yml: Action that routes requests to skill/custom-agent/mcp-server/iac/other labels
yprikhodko
reviewed
Aug 24, 2026
yprikhodko
reviewed
Aug 24, 2026
yprikhodko
reviewed
Aug 24, 2026
yprikhodko
reviewed
Aug 24, 2026
…bels - Use absolute URL for CONTRIBUTING.md link in request form (relative path unreliable in issue-form markdown) - Rename bug-form labels: 'Describe the bug', 'Expected behaviour', 'Environment details'
yprikhodko
reviewed
Aug 25, 2026
| - type: checkboxes | ||
| id: tool-type | ||
| attributes: | ||
| label: What type of tool is this? |
Contributor
There was a problem hiding this comment.
Suggested change
| label: What type of tool is this? | |
| label: Select the type of tool this is related to |
yprikhodko
reviewed
Aug 25, 2026
| - label: Skill | ||
| - label: Custom agent | ||
| - label: MCP server | ||
| - label: IaC |
Contributor
There was a problem hiding this comment.
Suggested change
| - label: IaC | |
| - label: IaC (Infrastructure as Code) template |
yprikhodko
reviewed
Aug 25, 2026
| - type: textarea | ||
| id: problem | ||
| attributes: | ||
| label: What problem are you trying to solve, and why is it hard? |
Contributor
There was a problem hiding this comment.
Suggested change
| label: What problem are you trying to solve, and why is it hard? | |
| label: What problem are you trying to solve? |
yprikhodko
reviewed
Aug 25, 2026
| name: Bug report | ||
| description: Report a problem with an existing skill, custom agent, MCP server, or IaC template. | ||
| title: "[bug]: <short description>" | ||
| labels: ["bug"] |
Contributor
There was a problem hiding this comment.
Suggested change
| labels: ["bug"] | |
| labels: ["bug", "needs-triage"] |
Adding needs-triage on submission fixes that: new issues land in a clean is:open label:needs-triage filter, and removing the label becomes the explicit "I've looked at this" signal.
yprikhodko
reviewed
Aug 25, 2026
| name: Suggest a new tool | ||
| description: Suggest a new skill, custom agent, MCP server, IaC template, or other tool for the roadmap. The team will review. | ||
| title: "[request]: <short description>" | ||
| labels: ["request"] |
Contributor
There was a problem hiding this comment.
Suggested change
| labels: ["request"] | |
| labels: ["request", "needs-triage"] |
yprikhodko
reviewed
Aug 25, 2026
yprikhodko
left a comment
Contributor
There was a problem hiding this comment.
I've finished review, left few more comments
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
Adds structured GitHub issue forms and automatic label-based routing to support the roadmap Project (
tools-for-devops-agent-roadmap).community-request.yml— roadmap intake form for suggesting a new skill, custom agent, MCP server, IaC template, or other tool. Applies therequestlabel on submission. Tool-type is a multi-select (a request can span more than one type, e.g. a skill plus a supporting MCP server).bug-report.yml— form for reporting problems with existing tools. Applies thebuglabel. Intentionally kept off the roadmap.config.yml— contact links (Contribution guidelines, Security reporting). Blank issues left enabled.label-tool-type.yml— GitHub Action that reads the request form's tool-type checkboxes and applies routing labels (skill/custom-agent/mcp-server/iac/other). Gated on therequestlabel so it never touches bug reports.How routing works
requeston submit.label:request) pulls the issue onto the board — bugs and untemplated issues stay off.label:skill, etc.). The "All Items" tab stays unfiltered.Follow-up (Project UI, not in this PR)
GitHub Project workflows and view filters are configured in the Project UI, not in the repo:
is:issue is:open label:requestlabel:skill,label:custom-agent,label:mcp-server,label:iacThe seven supporting labels (
request,bug,skill,custom-agent,mcp-server,iac,other) have already been created in the repo.Testing