Repository navigation
ci: allow dispatching workflow triage via label - #20042
Conversation
There was a problem hiding this comment.
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 or learn how to get started.
Co-authored-by: Copilot <[email protected]>
| if: inputs.cleanup | ||
| env: | ||
| BUCKET_PREFIX: "gs://coder-traiage-outputs/traiage" | ||
| CODER_USERNAME: ${{ steps.get-coder-username.outputs.coder_username }} |
There was a problem hiding this comment.
Thoughts about echoing into the env file rather than pulling from output?
There was a problem hiding this comment.
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 into GITHUB_ENV it's easier to mix up the order imo.
Allows creating a task for an issue if a label 'traiage' is set.
Requires membership of the
coderorg to run.Manual workflow_dispatch: https://github.com/coder/coder/actions/runs/18158719999/job/51684512634