Repository navigation
chore: set issue type and labels when creating issues via CLI - #5969
Merged
Merged
Conversation
Issue forms apply their type and labels only through the web form, so issues created with gh by agents had neither and needed manual triage. Fixes #5968
sdangol
approved these changes
Nov 14, 2026
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.
Summary
Issue forms apply their
type:andlabels:keys only when the issue is submitted through the web form, so issues that agents create with thecreate-issueskill had neither. The skill now has agents pass both togh issue create.Changes
.agents/skills/create-issue/SKILL.mdnow lists the issue type among the things the template defines, and tells agents to read the template'stype:key along withlabels:.gh issue create --type <type> --label <label> ...) and says why: GitHub applies them only through the web form.documentation_improvements.ymlto the list of templates to choose from. It was missing, so the skill never chose the Docs template.Issue number: closes #5968
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.