Add SOURCE_REF and CI tuple bookkeeping check#71
Merged
Conversation
Fail CI when HEAD diverges from SOURCE_REF so spec pins/matrix can record the SDK commit in the ecosystem tuple.
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.
Summary
SOURCE_REFset to currentmaincommit.scripts/check-source-ref.shin CI before signing fixture sync.Test plan
python3 -m pytestbash scripts/check-source-ref.shRequires intentproof-spec PR that records this SHA in pins/matrix (merge spec
first or in the same release window).