So I setup the auto approve pull request automation, which auto approves low risk PRs and assigns reviewers for higher risk ones.
However… it can’t approve those PRs created by previous/other cursor automations This prevents us from using automations fully « automated » to do minor documentation or low risk updates, without having to still manually click approve. Which was just the kind of PRs we wanted to have auto approved in the first place !
Could there be a different identity used between creation and review ? I guess I can just setup a GitHub app, create a key with approval, and set that up with a GitHub mcp tool in the automation. It’s just much more cumbersome
Hey, this isn’t a Cursor bug, it’s a GitHub limitation. The same actor can’t create a PR and approve it at the same time. Right now, all Cursor automations run under the same identity, cursor[bot], so one automation can’t approve what another automation created.
Two workarounds:
Personal GitHub OAuth: connect your GitHub in Dashboard > Integrations > GitHub. Then the PR-creating automation will be attributed to you, and the approve automation will still run as cursor[bot]. Since the identities are different, GitHub will allow it.
A separate GitHub App via MCP, like you described. It works, but it’s more work to set up.
We have a feature request in the backlog to let you configure attribution for automation-created PRs, so create and review can use different identities. I can’t share an ETA, but it’s on our radar. If I get an update, I’ll reply in the thread.
This prevents us from using automations fully « automated » to do minor documentation or low risk updates, without having to still manually click approve. Which was just the kind of PRs we wanted to have auto approved in the first place !