ci: add issue-triage bots (stale, label-actions, area-labeler)#596
Open
DeusData wants to merge 1 commit into
Open
ci: add issue-triage bots (stale, label-actions, area-labeler)#596DeusData wants to merge 1 commit into
DeusData wants to merge 1 commit into
Conversation
Three native GitHub Actions to automate the mechanical parts of issue triage: - stale.yml: actions/stale scoped to the awaiting-reporter label — warns at 21 days idle, closes at 35, auto-resets when the reporter replies. Never touches PRs or unlabeled issues. - label-actions.yml + .github/label-actions.yml: posts a templated comment when duplicate or awaiting-reporter is applied (duplicates are linked, not auto-closed). - issue-labeler.yml + .github/issue-labeler.yml: adds area labels (windows, stability/performance, parsing/quality, editor/integration, ux/behavior, cypher, language-request) from title/body keywords. Additive only; base bug/enhancement labels still come from the forms. All third-party actions pinned to full commit SHAs with least-privilege per-job permissions (issues: write only where required). Signed-off-by: Martin Vogel <martin.vogel.tech@gmail.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Three native GitHub Actions that automate the mechanical parts of issue triage. The judgment parts (writing a real first reply, accurately connecting duplicates, picking the right area label initially) stay manual — these bots just take the repetitive load off.
1. Stale lifecycle —
awaiting-reporter→ warn → close.github/workflows/stale.yml(actions/stale)awaiting-reporter— never on PRs, never on unlabelled issues.stale; 14 more days → closes asnot planned.staleand resets the clock automatically.workflow_dispatch).This replaces the hand-maintained stale-watch table.
2. Templated label comments
.github/workflows/label-actions.yml+.github/label-actions.yml(dessant/label-actions)duplicate→ posts a "this is a duplicate, see the linked issue" comment. (We link, not auto-close — the auto-close lines are present but commented out.)awaiting-reporter→ posts the "we need version + a public repro" template, so you don't retype it.3. Keyword area-labeler
.github/workflows/issue-labeler.yml+.github/issue-labeler.yml(github/issue-labeler)windows,stability/performance,parsing/quality,editor/integration,ux/behavior,cypher,language-request.sync-labels: 0) — never removes a label set by hand. Basebug/enhancementkeep coming from the issue forms.Labels added (already created on the repo)
awaiting-reporter— waiting on the reporter; drives the stale workflow.stale— applied by the bot before closing.Security
actions/stalev10.3.0,dessant/label-actionsv5.0.3,github/issue-labelerv3.4.contents: read;issues: writegranted only on the jobs that need it. No PR write, no broad scopes.Notes
stale.yml, comment text inlabel-actions.yml, regexes inissue-labeler.yml.