34 lines
2.0 KiB
YAML
34 lines
2.0 KiB
YAML
name: "Close Stale Issues"
|
|
on:
|
|
workflow_dispatch:
|
|
schedule:
|
|
- cron: "0 0 * * *"
|
|
|
|
jobs:
|
|
stale:
|
|
if: github.repository_owner == 'ory'
|
|
runs-on: ubuntu-latest
|
|
steps:
|
|
- uses: actions/stale@v3
|
|
with:
|
|
repo-token: ${{ secrets.GITHUB_TOKEN }}
|
|
stale-issue-message: |
|
|
I am marking this issue as stale as it has not received any engagement from the community or maintainers in over half a year. That does not imply that the issue has no merit! If you feel strongly about this issue
|
|
|
|
- open a PR referencing and resolving the issue;
|
|
- leave a comment on it and discuss ideas how you could contribute towards resolving it;
|
|
- open a new issue with updated details and a plan on resolving the issue.
|
|
|
|
We are cleaning up issues every now and then, primarily to keep the 4000+ issues in our backlog in check and to [prevent](https://www.jeffgeerling.com/blog/2020/saying-no-burnout-open-source-maintainer) [maintainer](https://www.jeffgeerling.com/blog/2016/why-i-close-prs-oss-project-maintainer-notes) [burnout](https://docs.brew.sh/Maintainers-Avoiding-Burnout). Burnout in open source maintainership is a [widespread](https://opensource.guide/best-practices/#its-okay-to-hit-pause) and serious issue. It can lead to severe personal and health issues as well as [enabling catastrophic](https://haacked.com/archive/2019/05/28/maintainer-burnout/) [attack vectors](https://www.gradiant.org/en/blog/open-source-maintainer-burnout-as-an-attack-surface/).
|
|
|
|
Thank you for your understanding and to anyone who participated in the issue! 🙏✌️
|
|
|
|
If you feel strongly about this issues and have ideas on resolving it, please comment. Otherwise it will be closed in 30 days!
|
|
stale-issue-label: 'stale'
|
|
exempt-issue-labels: 'bug,blocking,docs'
|
|
days-before-stale: 180
|
|
days-before-close: 30
|
|
exempt-milestones: true
|
|
exempt-assignees: true
|
|
only-pr-labels: 'stale'
|