Develop#106
Merged
Merged
Conversation
…ss required checks The back-merge job tagged its "sync main into develop" commit with a CI-skip marker. No workflow runs on pushes to develop, so the marker skipped nothing there — but it rode along on the merge commit, and when develop was opened as a PR to main that commit became the PR head. GitHub Actions then skipped the pull_request CI run entirely, so the required "Tests (fast)" and "Lint" checks never reported and the develop->main PR (#106) was stuck BLOCKED with no way to satisfy the protect-main ruleset. Drop the marker from the commit message. ci() type → no semantic release. Co-Authored-By: Claude Opus 4.8 (1M context) <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.
No description provided.