Files
deusdata--codebase-memory-mcp/.github/label-actions.yml
Martin Vogel c37848a73c
DCO / dco (push) Has been cancelled
ci: add issue-triage bots (stale, label-actions, area-labeler)
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>
2026-06-24 01:18:29 +02:00

36 lines
1.4 KiB
YAML

# Config for dessant/label-actions (.github/workflows/label-actions.yml).
# Each top-level key is a label; when that label is added to an issue, the
# listed actions run. See https://github.com/dessant/label-actions
# When a maintainer marks an issue as a duplicate.
duplicate:
comment: >
Thanks for raising this! It looks like a duplicate of an existing issue —
the canonical one is linked above. Continuing the discussion there keeps
everything in one place. We leave this open for visibility; a maintainer
will close it once it's fully covered.
# We intentionally do NOT auto-close duplicates (we prefer linking).
# To auto-close instead, uncomment the two lines below:
# close: true
# close-reason: not planned
# When a maintainer marks an issue as waiting on the reporter.
# (The stale workflow then warns at 21 days and closes at 35.)
awaiting-reporter:
comment: >
Thanks for the report! To move this forward we need a bit more so we can
reproduce it ourselves:
- the `codebase-memory-mcp --version` you're on
- the exact steps or command you ran
- a **public** repo (or a small dummy snippet) that shows the problem —
please don't paste proprietary code
Once that's here we'll pick it straight back up. Heads-up: issues left
`awaiting-reporter` are automatically closed after a few weeks of silence,
but a comment reopens the door anytime.