Repository navigation
Coverage: publish onto the branch's current head - #15
Merged
Merged
Conversation
A dispatched run checks out the commit the branch had when the run was queued. When another coverage run's docs commit landed in the meantime (runs wait in the concurrency group), the docs push was rejected as a non-fast-forward and the site step skipped. Publish now writes the README section into the branch's current README, and the docs commit goes on that head with only README.md and the version's coverage page. Assisted-by: Claude Opus 5.5
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.
A dispatched coverage run checks out the commit the branch had when it was queued. If another coverage run's docs commit lands while it waits (runs queue in the concurrency group), its docs push is rejected as a non-fast-forward and the site step is skipped. This is what would have happened tonight with 3.2.3 queued behind 4.1.0.
publish_coverage.jlwrites this version's section.git reset FETCH_HEAD, then commit only README.md and the version's coverage page on that head.Tested by running both steps' run blocks from the workflow against a local origin with a depth-1 checkout. Master's workflow: push rejected. This branch: ok when the other run measured the other version (result identical to the real fed4dcd), the same version (this run's page and section win, nothing mixed), or when nothing landed in between.
🤖 Generated with Claude Code