NotificationsYou must be signed in to change notification settings
Fork1k
Star11.1k

ci: allow dispatching workflow triage via label#20042

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 ourterms of service andprivacy statement. We’ll occasionally send you account related emails.

Already on GitHub?Sign in to your account

Jump to bottom

Merged

johnstcn merged 10 commits intomainfromcj/traiage-label

Oct 1, 2025

Merged

ci: allow dispatching workflow triage via label#20042

johnstcn merged 10 commits intomainfromcj/traiage-label

Oct 1, 2025

+72 −13

Conversation

Copy link

Member

johnstcn commentedSep 30, 2025•
edited
Loading

Allows creating a task for an issue if a label 'traiage' is set.
Requires membership of thecoder org to run.

Manual workflow_dispatch:https://github.com/coder/coder/actions/runs/18158719999/job/51684512634

ci: allow dispatching workflow triage via label

5ed3bb0

johnstcn self-assigned this

Sep 30, 2025

johnstcn requested a review fromCopilot

September 30, 2025 15:52

CopilotAI reviewed

Sep 30, 2025

View reviewed changes

Copy link

Contributor

CopilotAI left a comment

Choose a reason for hiding this comment

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

Pull Request Overview

This PR adds the ability to trigger the AI triage workflow automatically when an issue is labeled with 'traiage', expanding beyond the existing manual workflow dispatch trigger. The changes introduce user permission checks, automatic GitHub issue commenting, and improved task status monitoring.

Adds automatic triggering when issues are labeled with 'traiage'
Implements user permission validation requiring write access
Adds automatic commenting on GitHub issues when tasks are created

_{Tip: Customize your code reviews with copilot-instructions.md.Create the file orlearn how to get started.}

.github/workflows/traiage.yamlShow resolvedHide resolved

.github/workflows/traiage.yaml OutdatedShow resolvedHide resolved

johnstcnand others added2 commits

September 30, 2025 16:57

Update .github/workflows/traiage.yaml

565e945

Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>

fixup! Update .github/workflows/traiage.yaml

7478df1

johnstcn requested review frommafredri andDanielleMaywood

September 30, 2025 17:14

johnstcn mentioned this pull request

Sep 30, 2025

tasks: create internal github -> coder -> pr workflowcoder/internal#1031

Open

7 tasks

johnstcn added6 commits

September 30, 2025 23:44

Merge branch 'main' into cj/traiage-label

75c2d1b

local testing with nektos/act

edb4679

GITHUB_TOKEN

6920054

since when is it GH_TOKEN?

402f752

fixup! since when is it GH_TOKEN?

210ec2d

scoping

0f74b89

mafredri reviewed

Oct 1, 2025

View reviewed changes

.github/workflows/traiage.yaml OutdatedShow resolvedHide resolved

.github/workflows/traiage.yaml

		if:inputs.cleanup
		env:
		BUCKET_PREFIX:"gs://coder-traiage-outputs/traiage"
		CODER_USERNAME:${{ steps.get-coder-username.outputs.coder_username }}

Copy link

Member

mafredriOct 1, 2025

Choose a reason for hiding this comment

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

Thoughts about echoing into the env file rather than pulling from output?

Copy link

MemberAuthor

johnstcnOct 1, 2025

Choose a reason for hiding this comment

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

I'm mostly indifferent, but I think explicitly pulling from output makes it easier to see the dependency chain between the steps. If you just dump everything intoGITHUB_ENV it's easier to mix up the order imo.