repo sync: Use the new merge-upstream API if available#4942
Merged
Conversation
This helps avoid the errors when a new commit from upstream is not yet available in the fork, resulting in a HTTP 404 when trying to update the ref in the fork. If the merge-upstream API is unavailable (404) or errors out (409/422), the functionality falls back to the previous functionality of manually updating refs. This ensures that `--force` still has effect.
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.
This helps avoid the errors when a new commit from upstream is not yet available in the fork, resulting in a HTTP 404 when trying to update the ref in the fork.
If the merge-upstream API is unavailable (404) or errors out (409/422), the functionality falls back to the previous functionality of manually updating refs. This ensures that
--forcestill has effect.Fixes #4907