ci: add automated issue labeling workflow#2359
Open
yonib05 wants to merge 3 commits into
Open
Conversation
Adds three independent labelers that run in parallel on issue open/edit: - area: classifies by technical subsystem (area-provider, area-mcp, etc.) - type: classifies as bug/enhancement/question/chore - language: identifies python vs typescript Uses the shared issue-labeler action from devtools which validates LLM output against the hardcoded label allowlists in .github/labelers/.
![github-actions[bot]](https://avatars.githubusercontent.com/in/15368?s=60&v=4){kind=small}
Contributor
|
Assessment: Comment Clean and well-structured workflow addition that follows existing repo patterns ( Review Themes
Nice work overall—the parallel job design and sparse checkout are thoughtful efficiency choices. |
- Drop edited trigger to avoid redundant re-classification on minor edits - Add comment clarifying max_labels is intentionally omitted for area labels - Add disambiguation hints for commonly confused label pairs (mcp vs tool, provider vs async, hooks vs others) - Add guidance for cross-SDK language issues
Contributor
|
Assessment: Approve All 4 suggestions from the previous review have been addressed cleanly. The updated PR is well-structured, with appropriate trigger scoping ( Changes Verified
No remaining concerns — ready to merge once the devtools dependency (strands-agents/devtools#55) is merged. |
yonib05
changed the title
yonib05
added
area-community
lizradway
reviewed
Jun 1, 2026
| Provider-specific async/streaming bugs belong to area-provider, not area-async. | ||
| Issues about hook lifecycle events belong to area-hooks even if they mention tools or agents. | ||
|
|
||
| labels: |
Member
There was a problem hiding this comment.
interventions label is only in TS repo, so i don't think some TS labels got ported over.
lizradway
reviewed
Jun 1, 2026
| labels: | ||
| python: | ||
| description: "Issue relates to the Python SDK (strands-py/, .py files, pip, pyproject.toml)" | ||
| javascript: |
lizradway
reviewed
Jun 1, 2026
| # Classifies issues by technical area/subsystem. | ||
|
|
||
| instructions: | | ||
| This is the Strands Agents SDK repository (Python + TypeScript monorepo). |
Member
There was a problem hiding this comment.
should this also add labels for docs?
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
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.
Description
Adds automated issue labeling using the shared
issue-labeleraction from devtools. Three independent labelers run in parallel on every issue open/edit:Each labeler has its own config in
.github/labelers/defining the valid label set and classification instructions. The LLM output is validated against these configs so it can only apply labels that exist in the allowlist.Related Issues
Depends on strands-agents/devtools#55
Type of Change
New feature
Testing
Checklist
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.