-
Notifications
You must be signed in to change notification settings - Fork 254
feat(auto-triage): assign community label for non-contributor and read-only issues
#18353
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
| Original file line number | Diff line number | Diff line change | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
|
@@ -122,9 +122,10 @@ When triggered by an issue event (opened/edited) or scheduled run, analyze issue | |||||||||
| When an issue is opened or edited: | ||||||||||
|
|
||||||||||
| 1. **Analyze the issue** that triggered this workflow (available in `github.event.issue`) | ||||||||||
| 2. **Classify the issue** based on its title and body content | ||||||||||
| 3. **Apply appropriate labels** using the `add_labels` tool | ||||||||||
| 4. If uncertain, add the `needs-triage` label for human review | ||||||||||
| 2. **Check if the author is a community member** — if `author_association` is `NONE`, `FIRST_TIME_CONTRIBUTOR`, `FIRST_TIMER`, or `CONTRIBUTOR`, and the author is **not** a bot (`user.type != "Bot"` and login does not end with `[bot]`), include `community` in the labels to apply | ||||||||||
| 3. **Classify the issue** based on its title and body content | ||||||||||
| 4. **Apply all labels** (including `community` if applicable) in a single `add_labels` call | ||||||||||
| 5. If uncertain about classification, add the `needs-triage` label for human review | ||||||||||
|
|
||||||||||
| ### On Scheduled Runs (Every 6 Hours) | ||||||||||
|
|
||||||||||
|
|
@@ -180,6 +181,14 @@ Apply component labels based on mentioned areas: | |||||||||
| - `priority-high` - Contains "critical", "urgent", "blocking", "important" | ||||||||||
| - `good first issue` - Explicitly labeled as beginner-friendly or mentions "first time", "newcomer" | ||||||||||
|
|
||||||||||
| ### Community Label | ||||||||||
|
|
||||||||||
| Apply the `community` label when: | ||||||||||
| - `author_association` is `NONE`, `FIRST_TIME_CONTRIBUTOR`, `FIRST_TIMER`, or `CONTRIBUTOR` | ||||||||||
| - **AND** the author is **not** a bot (`user.type != "Bot"` and login does not end with `[bot]`) | ||||||||||
|
Comment on lines
+187
to
+188
|
||||||||||
| - `author_association` is `NONE`, `FIRST_TIME_CONTRIBUTOR`, `FIRST_TIMER`, or `CONTRIBUTOR` | |
| - **AND** the author is **not** a bot (`user.type != "Bot"` and login does not end with `[bot]`) | |
| - `github.event.issue.author_association` is `NONE`, `FIRST_TIME_CONTRIBUTOR`, `FIRST_TIMER`, or `CONTRIBUTOR` | |
| - **AND** the author is **not** a bot (`github.event.issue.user.type != "Bot"` and `github.event.issue.user.login` does not end with `[bot]`) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Step 2 hard-codes the full community/bot criteria inline, but the same rule is repeated later under “### Community Label”. Keeping the criteria in two places risks them drifting; consider making step 2 reference the “Community Label” rule (or otherwise centralize the criteria) and keep the detailed condition in only one section.