Repository navigation
docs: Re-run the example lint on every label change - #4
Merged
Merged
Conversation
The example workflow skipped its job for labels other than the override label, and GitHub shows the latest run as a pull request's result, so adding any label after a failure turned the check green. Every label change now re-runs the lint. Co-Authored-By: Claude Opus 5.5 <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
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.
The README's example workflow re-runs the lint on every label change instead of skipping its job for labels other than the override label. GitHub shows a pull request's latest run as its result, so a skipped run let any label added after a failure turn the check green; sentry's workflow had the same bug, caught by Cursor Bugbot in getsentry/sentry#128259.
🤖 Generated with Claude Code