Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Action fails due to "HttpError: There are merge conflicts" #24

Closed
matchai opened this issue Dec 21, 2021 · 1 comment
Closed

Action fails due to "HttpError: There are merge conflicts" #24

matchai opened this issue Dec 21, 2021 · 1 comment

Comments

@matchai
Copy link

matchai commented Dec 21, 2021

Hi there,

Thank you for your excellent action, Mislav. We've been using it as part of our release process over at https://github.com/starship/starship for a while now.

With the latest release of the action, we started seeing a strange failure with the following error:

POST /repos/Homebrew/homebrew-core/forks - 202 in 316ms
POST /repos/matchai/homebrew-core/merge-upstream - 409 in 1071ms
Error: HttpError: There are merge conflicts

Full logs: https://github.com/starship/starship/runs/4599656801?check_suite_focus=true#step:2:17

@mislav
Copy link
Owner

mislav commented Dec 21, 2021

@matchai Thank you for reporting. I'll try to address this, but in the meantime, the workaround would be to drop down to git, check out the default branch of matchai/homebrew-core, hard-reset it to the latest state of the default branch in upstream, and force-push that to your fork. The idea is that the default branch in your fork always tracks the latest state in upstream, but that can't happen if the branch in your fork has diverged for some reason.

@mislav mislav closed this as completed in 0104f12 Dec 23, 2021
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

No branches or pull requests

2 participants