update-checkout: Do not update repository if not listed in the given branch-scheme #61275
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
AnthonyLatsis
force-pushed
the
scheme-oriented-checkouts
branch
2 times, most recently
from
8eb73c6 to
6ffcbad
Compare
…branch-scheme Consider two branch-schemes, where the second is a subset of the first. Suppose repositories have been cloned using the first branch scheme. Previously, a successive update using the second branch-scheme would cause update-checkout to fail in an attempt to query the branch-scheme about the target branch for a repository it does not map, even though the update, given no further errors, can be considered successful.
AnthonyLatsis
force-pushed
the
scheme-oriented-checkouts
branch
from
6ffcbad to
abd17b6
Compare
AnthonyLatsis
added
contributor experience
update-checkout
|
@swift-ci please Python lint |
|
@gottesmm ping |
|
@shahmishal ping |
gottesmm
approved these changes
Oct 14, 2022
|
@swift-ci please smoke test |
|
Thanks for reviewing! |
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.
Consider two branch-schemes, where the second is a subset of the first. Suppose repositories have been cloned using the first branch scheme. Previously, a successive update using the second branch-scheme would cause update-checkout to fail in an attempt to query the branch-scheme about the target branch for a repository it does not map, even though the update, given no further errors, can be considered successful.