Skip to content

Add issue forms for tool requests and bugs, with tool-type auto-labeling - #64

Open
udid-aws wants to merge 2 commits into
mainfrom
add-community-request-issue-template
Open

Add issue forms for tool requests and bugs, with tool-type auto-labeling#64
udid-aws wants to merge 2 commits into
mainfrom
add-community-request-issue-template

Conversation

@udid-aws

Copy link
Copy Markdown
Contributor

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 the request label 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 the bug label. 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 the request label so it never touches bug reports.

How routing works

  1. Request form applies request on submit.
  2. The Action adds tool-type labels based on the checked boxes.
  3. The Project's Auto-add workflow (filtered to label:request) pulls the issue onto the board — bugs and untemplated issues stay off.
  4. Each roadmap tab filters by its tool-type label (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:

  • Auto-add to project → filter is:issue is:open label:request
  • Item added to project → set Status = Backlog
  • Per-tab filters: label:skill, label:custom-agent, label:mcp-server, label:iac

The seven supporting labels (request, bug, skill, custom-agent, mcp-server, iac, other) have already been created in the repo.

Testing

  • Validated all four YAML files parse successfully.
  • Issue forms take effect once merged to the default branch.

- 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
Comment thread .github/ISSUE_TEMPLATE/community-request.yml Outdated
Comment thread .github/ISSUE_TEMPLATE/bug-report.yml Outdated
Comment thread .github/ISSUE_TEMPLATE/bug-report.yml Outdated
Comment thread .github/ISSUE_TEMPLATE/bug-report.yml Outdated
…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'
- type: checkboxes
id: tool-type
attributes:
label: What type of tool is this?

@yprikhodko yprikhodko Aug 25, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
label: What type of tool is this?
label: Select the type of tool this is related to

- label: Skill
- label: Custom agent
- label: MCP server
- label: IaC

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
- label: IaC
- label: IaC (Infrastructure as Code) template

- type: textarea
id: problem
attributes:
label: What problem are you trying to solve, and why is it hard?

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
label: What problem are you trying to solve, and why is it hard?
label: What problem are you trying to solve?

name: Bug report
description: Report a problem with an existing skill, custom agent, MCP server, or IaC template.
title: "[bug]: <short description>"
labels: ["bug"]

@yprikhodko yprikhodko Aug 25, 2026

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

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.

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"]

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Suggested change
labels: ["request"]
labels: ["request", "needs-triage"]

@yprikhodko yprikhodko left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I've finished review, left few more comments

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants