meshcore-client

Commit Graph

Author	SHA1	Message	Date
Strycher	f6ebeef4f7	chore(#148 ): auto-triage user-submitted issues (flag + P2/Backlog) New workflow .github/workflows/triage-user-issues.yml. On issues:opened, if the author is external (author_association not OWNER/MEMBER/COLLABORATOR), apply user-submitted + priority:P2 + board:backlog using PROJECT_PAT so the existing sync-labels-to-board.yml fires and sets Status=Backlog / Priority=Medium on board #2. Maintainer-opened issues are untouched. type: is left for manual triage. workflow_dispatch entrypoint added for manual re-triage and the post-merge live test: both triggers require the workflow to be on the default branch first (issues:-triggered workflows only run from default; a new workflow_dispatch is only dispatchable once on default), so validation happens after the merge to dev. Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>	3 weeks ago

Author

SHA1

Message

Date

Strycher

f6ebeef4f7

chore(#148 ): auto-triage user-submitted issues (flag + P2/Backlog)

New workflow .github/workflows/triage-user-issues.yml. On issues:opened, if
the author is external (author_association not OWNER/MEMBER/COLLABORATOR),
apply user-submitted + priority:P2 + board:backlog using PROJECT_PAT so the
existing sync-labels-to-board.yml fires and sets Status=Backlog /
Priority=Medium on board #2. Maintainer-opened issues are untouched. type:
is left for manual triage.

workflow_dispatch entrypoint added for manual re-triage and the post-merge
live test: both triggers require the workflow to be on the default branch
first (issues:-triggered workflows only run from default; a new
workflow_dispatch is only dispatchable once on default), so validation
happens after the merge to dev.

Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>

1 Commits (5eded9e33ca59cce2b986a347f3aa0996e82bcb3)