DIVE-4090: derive the file-size ratchet base from the merge commit, not a branch name and a pasted sha - #10
Merged
Conversation
…ot a branch name and a pasted sha Byte-identical to 5dive-ai/buzz's DIVE-4090 change (same three blobs): a resolver step before `File size policy` reads the ratchet base off the sync merge commit itself, fetch-depth returns to a plain 2, and the branch-name predicates plus the pasted week-3 sha are removed.
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.
Byte-identical mirror of the 5dive-ai/buzz DIVE-4090 PR (same commit body, same three blobs):
See that PR for the mechanism and the receipts. This branch is named
…-sync-derivedon purpose: itsResolve file size ratchet basestep must printratchet-base: HEAD^1 (no merge commit among this PR's 1 first-parent commit(s)).