ci: drop --depth=1 base fetch in migration-policy (false positives) - #34
Merged
Merged
Conversation
…ed false positives) The base ref was fetched --depth=1 while policy.yml checks out full history; the shallow graft made origin/BASE..HEAD reappear historical base commits after an Update-branch merge, tripping the commit-metadata rule. Fetch the base full-depth (matching the already-fixed variant in rustnzb).
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.
The base ref was fetched with
--depth=1while the workflow checks out full history; the shallow graft madeorigin/BASE..HEADreappear historical base commits after an Update-branch merge, tripping the commit-metadata rule on commits the PR never touched. Fetch the base full-depth, matching the already-fixed variant in rustnzb. No change to what the policy forbids.