Pull Requests - Auto-PR isn't creating pull requests

Symptoms

• Your CI/pipeline log says automatic pull request creation was initiated successfully for an issue type, but no pull request (or commit) actually appears in the repository or fix report.

• Auto-PR works for one SCM (for example, GitLab) but not another (for example, GitHub).

• The issue type is enabled for auto-PR in the project's fix policy, yet nothing is created.

Likely cause

Auto-PR is triggered, but the push silently fails because the SCM connection is using a stale or invalid credential. On GitHub specifically, a stale personal OAuth token is a common culprit — and if an org-level GitHub App is also installed, the Disconnect button on the Integrations page may not actually remove the OAuth token, so you can't refresh it from the UI.

Resolution

1. In the project's Fix Policy, confirm auto-PR is enabled for the issue type in question.

2. On the Integrations page, confirm the target SCM shows Connected and the token is valid with permission to create branches and pull/merge requests.

3. If the SCM credential is stale and you can't disconnect/refresh it from the UI, override it by adding a PAT via the Mobb CLI — a PAT added this way takes precedence over an existing OAuth token. See Add SCM Token Mode.

4. Re-run the flow and confirm pull requests are created.

If manual PR creation also fails, start with "Create a Pull Request" fails. Still stuck? Contact [e-mail].