docs: explain issue triage policy (#3725)
Some checks are pending
CI / build-check-test (push) Waiting to run

* docs: explain issue triage policy

* docs: clarify issue triage wording
This commit is contained in:
pidalf 2026-04-25 23:02:17 +02:00 committed by GitHub
parent d2f8bd6deb
commit 05f79b0851
No known key found for this signature in database
GPG key ID: B5690EEEBB952194

View file

@ -69,3 +69,25 @@ pi's core is minimal. If your feature does not belong in the core, it should be
## Questions?
Ask on [Discord](https://discord.com/invite/nKXTsAcmbT).
## FAQ
### Why are new issues and PRs auto-closed?
pi receives more issues than the maintainers can responsibly review in real time. Many reports do not meet the quality bar in this guide or do not follow CONTRIBUTING.md. Some are slung at the repository mindlessly via an agent instead of being reviewed and shaped by the person submitting them. Auto-closing creates a buffer so maintainers can review the tracker on their own schedule and reopen the issues that meet the quality bar.
### Why are weekend issues not reviewed?
Maintainers need uninterrupted time away from the issue tracker. Issues submitted Friday through Sunday are auto-closed and are not part of the Monday review queue. If a problem is urgent, ask on Discord and include the short version, a repro, and the relevant logs.
### Why do some issues get no reply?
A reply is maintenance work too. Low-signal issues, unclear reports, duplicates, and issues that do not follow this guide may be closed without discussion. This keeps time available for reproducible bugs, thoughtful requests, and contributors who have done the work to make their report actionable.
### Why not let AI triage everything?
AI can help group duplicates, summarize reports, and spot missing information. It is not trusted to make final maintainer decisions. Polished AI-generated issues can still be wrong, misleading, or expensive to investigate. Human review remains the final gate.
### Is this hostile to contributors?
No. It is a guardrail against burnout and tracker spam. Short, concrete, reproducible issues are welcome. Thoughtful contributions are welcome. Automated slop, entitlement, and large volumes of low-effort reports are not.