ci: convert stale PRs back to draft - #55
Merged
Merged
Conversation
✅ Deploy Preview for peaceful-pothos-9e62ce ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Same workflow as https://github.com/prosopo/captcha-private/pull/4117, copied verbatim — it reads
$GITHUB_REPOSITORY, so nothing is repo-specific.Daily cron plus a
workflow_dispatchwhose dry-run input defaults to true. Converts non-draft PRs with no update for 7 days back to draft, which stops them launching CI runs, and comments on each saying why and how to undo it (gh pr ready <n>).Excluded: PRs with auto-merge enabled (drafting one silently cancels its merge, since converting to draft disables auto-merge and re-readying does not restore it), approved PRs, and anything labelled
keep-ready. That label does not exist in this repo yet, so the opt-out is inert until it is created.The 7-day threshold is the review question; it is a dispatch input as well as a default.
Suggested first step after merge: dispatch it with the dry run left on and read the list before letting the schedule touch anything.