-
Notifications
You must be signed in to change notification settings - Fork 31
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
PR gets merged before all workflows were successful #1212
Comments
This was discussed (but no solution) here: https://stackoverflow.com/questions/67721399/run-a-workflow-when-multiple-other-workflows-have-finished-in-github-actions. This looks like a promising approach, but have not tested: https://github.com/marketplace/actions/wait-on-check |
Isn't it because dependabot has been added as an admin, and the repo is set to not include administrators in the merge check that it gets merged? or is this something else? |
@dunyakirkali I tried looking into this, and I believe @rbubley is right: the problem here is that in the example that @DanielBadura shared
there are multiple workflows, and looking at the GitHub docs, in particular
so as soon as one of the workflow finishes, this will be true: |
Maybe this should then be documented here since it can be misleading right now. |
As described in ridedott/merge-me-action#1212, the action runs as soon as any workflow in workflows completed. This means that it usually ran after linting the Java files and thus ignored if the CI failed. Ignoring the linting workflow is not optimal. However, the current behavior is way worse. Also, merge-me is meant for dependabot PRs which should not produce linting issues in general.
How would you describe the issue?
First, im not sure if this is a real bug here or something wrong with the config or gh workflow fail, maybe you can help me?
I recently added the workflow for auto-merges here: https://github.com/maglnet/ComposerRequireChecker/blob/3.6.x/.github/workflows/merge-dependabot-upgrades.yml
I wanted that these workflows listed there should all be successfully run and then the PR from dependatbot should be auto-merged.
Here one PR that was merged to fast: maglnet/ComposerRequireChecker#323
What are the expected results?
I would expect that all jobs need to be successful for the auto-merge.
What are the actual results?
The merge happens before all job were green.
How much does it hurt?
The solution would be to put all workflow files into one "Continues Integration" which is really not nice for maintainance. For example here: https://github.com/Roave/BetterReflection/tree/5.0.x/.github/workflows
The text was updated successfully, but these errors were encountered: