You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Upon merging while authenticated as a GitHub Application (bot), the Action prints the following error, but merges successfully anyway:
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.
The step doesn't fail despite the error, it simply returns successfully and the PR gets merged.
My suggestion would be to log the error below at the warning level instead of debug, because if the PR gets merged successfully on the first attempt, users don't get a chance to run their workflow again with debug messages enabled:
How would you describe the issue?
Upon merging while authenticated as a GitHub Application (bot), the Action prints the following error, but merges successfully anyway:
The step doesn't fail despite the error, it simply returns successfully and the PR gets merged.
Example from a recent workflow run: https://github.com/deviantony/docker-elk/actions/runs/3555997794/jobs/5973029853#step:3:12
The Application has the following permissions assigned:
How can we reproduce the issue?
What are the expected results?
Print a more detailed error: what failed and why.
Alternatively, don't print an error if the PR was merged successfully.
How much does it hurt?
1/10
The text was updated successfully, but these errors were encountered: