CI: check for pending releases - #36
Merged
Merged
Conversation
See <https://github.com/gap-actions/check-pending-release>. Assisted-by: Claude Code (Opus 5.5)
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #36 +/- ##
=======================================
Coverage 91.93% 91.93%
=======================================
Files 24 24
Lines 1526 1526
=======================================
Hits 1403 1403
Misses 123 123 🚀 New features to boost your workflow:
|
ruthhoffmann
approved these changes
Oct 2, 2026
ruthhoffmann
left a comment
ruthhoffmann
left a comment
Member
There was a problem hiding this comment.
Seems sensible. Looks good to me.
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
2 participants
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.
This adds a weekly workflow using check-pending-release. It opens a single issue (label
pending release) when there are commits since the last release that have been left untouched for at least 7 days, so finished work does not go unreleased. Changes to.githuband.gitignoredo not count. The issue is closed once a release is made; the job added torelease.ymlmakes that happen right after a release made with the release workflow.See the action's README for details and options, such as the quiet period or ignored paths.
🤖 Generated with Claude Code