Consider auto-closing release PRs if there is no activity for more than 6 hours
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 413
- Forks
- 308
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 253
Description
Sometimes a developer will open a release PR at the end of the day and leave it open overnight. This may make sense for them, but for developers in different time zones this can create a problem if they also want to create a release PR.
We should consider whether it makes sense to automatically close a release PR and delete the branch after 6 hours of inactivity.
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
The issue names no files, tests, or implementation entry point. Begin by locating the release-PR automation, then clarify how six hours of inactivity and branch deletion should be handled. Done means the behavior is specified and accounts for competing and overnight release PRs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100