ci: auto-reopen issue #5 if it's ever closed#70
Merged
Conversation
Issue #5 is the perpetual "run the tool against me" contribution target. Closing it (accidentally or by an aging bot) would break the documented contributor onboarding flow. This workflow listens for `issues: closed`, filters to #5, and reopens it with a short explanation comment. Complements pinning + locking #5: pin makes it visible, lock prevents drive-by comments, and this workflow prevents accidental closure. Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
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.
Summary
Adds a tiny GitHub Actions workflow that listens for
issues: closedand reopens #5 (with a short explanation comment) whenever it gets closed. #5 is the perpetual "rungem-contribute fix/submitagainst me" contribution target — accidentally closing it breaks the documented onboarding flow. This is the third leg of the protection stool alongside pinning and locking the issue, both of which were applied manually.Linked issue / ADR
Touches #5 (the issue this protects). No ADR: this is repo-tooling plumbing, not architecture.
Working agreement
gem-contribute fixandsubmitagainst me #5 open)bin/rubocopandbin/rspecpass locally — N/A, workflow-only change with no Ruby diffTest plan
End-to-end:
if: github.event.issue.number == 5guard prevents the job from running for any other issue close (the job step will be skipped, no runner time spent).Notes for reviewer
evergreen") but YAGNI — there's exactly one such issue and the explicit== 5guard is easier to reason about. Happy to generalize if we add a second evergreen issue.--commentis best-effort viaset -e: if commenting fails the workflow fails loudly rather than silently letting the issue stay closed. Reopen-then-comment ordering also means the issue is back open even if the comment call hits a transient error.🤖 Generated with Claude Code