Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
15 changes: 12 additions & 3 deletions .github/workflows/auto-triage-issues.md
Original file line number Diff line number Diff line change
Expand Up @@ -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
Copy link

Copilot AI Feb 25, 2026

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.

Suggested change
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
2. **Determine community status** — if the author meets the **Community Label** criteria (see [Community Label](#community-label) below), include `community` in the labels to apply

Copilot uses AI. Check for mistakes.
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)

Expand Down Expand Up @@ -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
Copy link

Copilot AI Feb 25, 2026

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

The bot check uses user.type and “login” without specifying the JSON path. To avoid ambiguity (and to match step 1’s github.event.issue reference), spell these out as github.event.issue.user.type and github.event.issue.user.login (and similarly github.event.issue.author_association).

Suggested change
- `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]`)

Copilot uses AI. Check for mistakes.

This label identifies issues opened by external community members and read-only contributors who are not team members or org members.

### Special Categories

- `automation` - Relates to automated workflows, bots, scheduled tasks
Expand Down