Add CI workflow to notify and auto-close stale PRs
Nobody has claimed this yet.
Assessment
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Newbie friendliness
- 72/100
Research direction
Start with the GitHub Actions workflow configuration and the actions/stale documentation. Configure scheduled and manual runs to process only pull requests, post a stale notification after inactivity, and close PRs that remain inactive. Done means the workflow runs in both modes and excludes issues.
Written by the indexing model from the issue text.
Description
Add a GitHub Actions workflow (actions/stale) that marks a pull request as stale after a period of inactivity and posts a notification comment, then automatically closes it if it stays inactive. Only PRs are processed; issues are excluded. Runs on a schedule and supports manual dispatch.
JIRA Issue: BA-6526
- Dominant language
- Python
- Stars
- 670
- Forks
- 183
- Avg merge
- 20h 35m
- Merged PRs (30d)
- 429
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from lablup/backend.ai
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
lablup/backend.ai#14890 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 80/100
lablup/backend.ai#14886 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 85/100
lablup/backend.ai#14485 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
lablup/backend.ai#14101 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
lablup/backend.ai#14080 ·
All issues in lablup/backend.ai
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 88/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 82/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
-
enhancement
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100