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

Pull request not merged #1149

Open
rtc11 opened this issue Oct 14, 2021 · 3 comments
Open

Pull request not merged #1149

rtc11 opened this issue Oct 14, 2021 · 3 comments
Labels
bug Something isn't working

Comments

@rtc11
Copy link

rtc11 commented Oct 14, 2021

How would you describe the issue?

Auto merge me from a workflow_run reports success with a generic error message.

How can we reproduce the issue?
On a public repository, use this exact setup:

Follow this guide: https://stefanzweifel.io/posts/2021/04/28/auto-merge-dependabot-pull-requests

Comment the pull request with @dependabot rebase to trigger the workflow where github..actor = dependabot[bot]

What are the expected results?
The pull request was merged

What are the actual results?
The action reports success ✅ , the pull-request was not merged, but this message is logged to the action console:

An error occurred while merging the Pull Request. This is usually caused by the base branch being out of sync with the target branch. In this case, the base branch must be rebased. Some tools, such as Dependabot, do that automatically.

How much does it hurt?
The action does not seem to work.

@rtc11 rtc11 added the bug Something isn't working label Oct 14, 2021
@amclin
Copy link

amclin commented Nov 1, 2021

This is driving me bonkers. Because dependabot runs on a schedule, multiple pull requests are created simultaneously and only the first one to complete gets automerged by merge-me-action

If you tell dependabot to rebase a PR, it does so successfully, but merge-me-action still reports the branch as out of sync. I can manually run the merge-me-action action again, which successfully merges, but that defeats the entire purpose.

@zaneselvans
Copy link

I'm also experiencing this behavior, e.g. on this workflow run. I had some successful automerges when I was setting things up initially, but now it seems to always fail in this same way.

@fizyk
Copy link

fizyk commented Dec 23, 2022

Happens for me on a single repository actually https://github.com/fizyk/pyramid_fullauth/actions/runs/3760533656/jobs/6391347098 other repositories with same settings are fine. And even if I ask dependabot to rebase or recreate the outcome is the same.... 😕

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants