Repository navigation
Verify merged bot source against trusted main - #27
Merged
Merged
Conversation
Contributor
|
@flemming-n-larsen Moderation needs your decision for The required check stays pending. After reviewing, use |
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 Publisher App opened catalog PR #26 after test bot PR #22 was merged. Verification checked the merged source PR's merge commit, but GitHub's current API version returned a null
merge_commit_shafor that PR. The verifier now compares the source bot directory at the PR head with trusted main, which confirms the merged bot files directly and fails closed if they differ.Validation: 47 Python tests passed (2 platform skips); git diff --check passed. Live evidence: Publisher App opened PR #26; verification completed but escalated on the null merge SHA. After merge, rerun publication for PR #22.