Repository navigation
Verify Patchling production by merge SHA - #20
Merged
Merged
Conversation
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 read-only Pages checker can now verify the full Git merge SHA against Cloudflare’s active production deployment. It checks the branch, successful deploy stage, GitHub trigger and skip state. The existing settings-only call keeps its current behavior.
The new check passed against production
b8b7936and rejected25c5d21, whoselanding/tree matches the current preview. All seven files matched Git on both the live site and the current preview. The local suite passed 274 tests with five optional checks skipped.Use
[CF-Pages-Skip]on this merge to preserve the existing production hold. Run the verifier after the next intended production merge. Live deployment · Current preview