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鈥檒l occasionally send you account related emails.
Already on GitHub? Sign in to your account
Option an option to use github's auto-merge feature #301
Comments
Would you be interested in sending a PR for this? |
Mmm, it won't happen soon to be honest. I'm not familiar with github actions and its api. But I found that to enable auto-merge PRs, we need to use graphql api https://github.com/orgs/community/discussions/24719#discussioncomment-3245222. |
馃帀 This issue has been resolved in version 3.5.0 馃帀 The release is available on: Your optic bot 馃摝馃殌 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Prerequisites
馃殌 Feature Proposal
Add an option to use github's auto-merge feature.
https://docs.github.com/en/pull-requests/collaborating-with-pull-requests/incorporating-changes-from-a-pull-request/automatically-merging-a-pull-request
This feature request may by related to #251.
Motivation
We don't use github actions and CI status checks are required to merge. When dependabot creates a PR, github-action-merge-dependabot immediately tries to merge the PR but fails because the required status checks are not successful. One idea is to use github's auto-merge feature and let github merge PRs instead of github-action-merge-dependabot.
Example
No response
The text was updated successfully, but these errors were encountered: