output labels #184
Merged
output labels #184
Conversation
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
…abels output type (#6) * Initial plan * Implement label output type for agentic workflows - Add LabelConfig struct with mandatory allowed field - Create add_labels.cjs JavaScript implementation - Update compiler parsing and job building logic - Add comprehensive tests for new functionality - Update schema to include labels output type - Add documentation for label addition feature The new label output type supports: - Mandatory allow-list enforcement - Strict addition-only operations (no removal) - Line-by-line parsing with safety checks - Subset validation of requested vs allowed labels - Clear error messages for validation failures Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> * Add max-count option to labels output and move label code to separate file Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> * Rename Label field to Labels to match YAML configuration Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --------- Co-authored-by: copilot-swe-agent[bot] <198982749+Copilot@users.noreply.github.com> Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
- Introduced `add_labels` job to add labels to issues and pull requests based on agent output. - Updated permissions and environment variables for label handling. - Enhanced error handling for context detection and label validation. - Updated documentation to specify allowed labels.
dsyme
reviewed
Aug 22, 2025
| labels: [automation, ai-agent] # Optional: labels to attach to PRs | ||
| draft: true # Optional: create as draft PR (defaults to true) | ||
| labels: | ||
| allowed: [triage, bug, enhancement] # Mandatory: allowed labels for addition |
Contributor
There was a problem hiding this comment.
It feels like if this allowed: is not specified, then the agentic part should be able to leave the chosen labels as data.
Contributor
There was a problem hiding this comment.
This applies to all the labels: features.
Contributor
Author
There was a problem hiding this comment.
I'll defer this to another PR.
…s and GitHub API integration
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Support for output that adds labels to current issue/pull_request