Repository navigation
ci: compare pull requests with their merge base when selecting suites - #834
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.
Why
The suite selection compared the pull request head with the current tip of
main. Whenmainmoved after the branch started, its new changes were counted as the pull request's, so a website-only pull request (#833) ran the full suite because of an unrelatedrelease-please-config.jsonchange.Changes
BASE...HEAD), matching the files GitHub shows as changed.Verification
release-please-config.jsonoutsidewebsite/, and the merge-base diff reports onlywebsite/files.