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
{{ message }}
This repository has been archived by the owner on Oct 11, 2023. It is now read-only.
Instead of having processbot tell if the statuses are passing through Webhook Events, which is e.g. susceptible to webhook delivery failures, it would be more reliable to enable/disable auto-merge through the GraphQL API.
The text was updated successfully, but these errors were encountered:
I don't think this would work as we're hoping for because some jobs spontaneously fail, as per #374 (comment), and that would cancel the automerge. Then, to re-enable the automerge in those scenarios we'd still rely on webhook deliveries.
I don't know if using automerge would provide a better flow than what we have currently, but I guess it's relevant to keep this issue open until a decision has been made about this.
Github implemented auto-merging this year and according to https://github.community/t/enabling-auto-merge-on-a-pr-using-the-api/150797/5 it is possible to enable it through the GraphQL API.
Instead of having processbot tell if the statuses are passing through Webhook Events, which is e.g. susceptible to webhook delivery failures, it would be more reliable to enable/disable auto-merge through the GraphQL API.
The text was updated successfully, but these errors were encountered: