Add ticket/issue/bug workflow to AGENTS.md - #26
Merged
Conversation
Document the steps to take when asked to add a ticket, issue, or bug: create the GitHub issue with the right labels, add it to the CLI Tools project, and set the Priority, Area, and Status fields. Includes the project and field/option IDs so the workflow can be followed directly.
Labels no longer use the area: prefix; reference the plain label names (feature, ux, agent, docs, security, testing, release) instead.
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
Adds an Adding a Ticket, Issue, or Bug section to AGENTS.md so future agent
sessions follow a consistent workflow when asked to file a ticket, issue, or bug.
The documented workflow covers all required steps:
area:*label.It includes the project ID and the field/option IDs so the steps can be run
directly without looking them up.
Notes