Skip to content

chore: add needs-triage caller workflow#905

Open
dussab wants to merge 1 commit into
mainfrom
add-needs-triage-workflow
Open

chore: add needs-triage caller workflow#905
dussab wants to merge 1 commit into
mainfrom
add-needs-triage-workflow

Conversation

@dussab
Copy link
Copy Markdown
Member

@dussab dussab commented May 29, 2026

Wires up the org-wide needs-triage reusable workflow. Any new or reopened issue is auto-labeled needs-triage; removing the label signals a maintainer has triaged it. Bot-authored issues are skipped.

Caller declares minimal permissions: issues: write and pins the reusable workflow to a commit SHA (v1). Verified end-to-end in the sandbox.

Copilot AI review requested due to automatic review settings May 29, 2026 10:53
@vercel
Copy link
Copy Markdown

vercel Bot commented May 29, 2026

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated (UTC)
docs-website Ready Ready Preview, Comment May 29, 2026 10:54am

Request Review

Copy link
Copy Markdown
Contributor

Copilot AI 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 a GitHub Actions workflow that calls Stacklok's org-wide reusable needs-triage workflow so newly opened or reopened issues are automatically labeled needs-triage for maintainer triage tracking.

Changes:

  • Add a new Needs Triage workflow triggered on issues events (opened, reopened).
  • Grant minimal issues: write permissions to allow labeling.
  • Call the pinned reusable workflow (stacklok/.github/.../needs-triage.yml) by commit SHA.

@dussab dussab requested a review from danbarr May 29, 2026 10:57
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants