Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Conversation

@mislav
Copy link
Contributor

@mislav mislav commented Dec 21, 2021

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.

Fixes #4907

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.
@mislav mislav requested a review from a team as a code owner December 21, 2021 15:48
@mislav mislav requested review from vilmibm and removed request for a team December 21, 2021 15:48
@mislav mislav merged commit eaa64df into trunk Dec 21, 2021
@mislav mislav deleted the repo-sync-merge-upstream branch December 21, 2021 16:05
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

"HTTP 404: Not Found" from gh repo sync

1 participant