From 56ceb90159a0cec5f62efefbf5a239ee858f05b5 Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 25 Feb 2026 13:03:22 +0000 Subject: [PATCH 1/2] Initial plan From d4dd71b9bc2e887ed88ca7ce6a2ad11978a4a68e Mon Sep 17 00:00:00 2001 From: "copilot-swe-agent[bot]" <198982749+Copilot@users.noreply.github.com> Date: Wed, 25 Feb 2026 13:09:24 +0000 Subject: [PATCH 2/2] feat(auto-triage): assign community label for non-contributor issues Apply `community` label to issues opened by: - NONE, FIRST_TIME_CONTRIBUTOR, FIRST_TIMER (external community) - CONTRIBUTOR (read-only role per @pelikhan's comment) Excludes bot authors (user.type == "Bot" or login ending in "[bot]"). Community label is included in a single add_labels call alongside content-based labels. Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com> --- .github/workflows/auto-triage-issues.md | 15 ++++++++++++--- 1 file changed, 12 insertions(+), 3 deletions(-) diff --git a/.github/workflows/auto-triage-issues.md b/.github/workflows/auto-triage-issues.md index 087e529b89..1022049016 100644 --- a/.github/workflows/auto-triage-issues.md +++ b/.github/workflows/auto-triage-issues.md @@ -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]`) + +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