Code Host Output
Code host integrations provide repositories and receive review output.
MergeLoom can publish to:
- GitHub pull requests
- GitLab merge requests
- Azure Repos pull requests
What the Code Host Must Allow
Section titled “What the Code Host Must Allow”The connected code host account or app must be able to:
- discover repositories
- clone or fetch the selected repository
- push a review branch
- create or update a PR/MR
- read PR/MR state for review and campaign feedback
Branch protection can still require human approval before merge. MergeLoom should create review output, not bypass your normal merge controls.
GitHub
Section titled “GitHub”GitHub uses a GitHub App for repository access, issue intake where used, branch push, and PR creation.
Recommended minimum repository permissions:
| Permission | Access |
|---|---|
| Contents | Read and write |
| Pull requests | Read and write |
| Issues | Read and write when GitHub Issues intake is used |
| Metadata | Read-only |
Install the app only on repositories MergeLoom should be allowed to work with.
GitLab
Section titled “GitLab”GitLab uses OAuth/token-backed access for GitLab Issues intake, repository access, and merge request creation.
Check:
- base URL and API URL match the GitLab host
- token has project access
- repository is synced and enabled
- branch push and MR creation are allowed
Azure Repos
Section titled “Azure Repos”Azure Repos output uses Azure DevOps access to clone/fetch/push and create pull requests.
Check:
- organization and project
- repository sync
- connected account permissions
- target branch
- branch policy behavior
The Azure path uses the connected Azure DevOps account for Git and PR API access. If publish fails, check that the account can push the review branch and create a pull request in the selected repository.
Cloud Hosted
Section titled “Cloud Hosted”Cloud Hosted workers use controller-managed, job-scoped repository access. The customer does not configure SSH keys on a worker.
Self Hosted
Section titled “Self Hosted”Self Hosted workers receive repository access details from the controller when they start a job. The default path does not require host-level SSH setup for GitHub or GitLab. Confirm the worker can reach the code host over the network.
Publish Failures
Section titled “Publish Failures”If the worker pushed a branch but the PR/MR creation failed, the customer job detail page can show Retry publish for failed standalone jobs with a publish_failed gate and stored branch artifacts.
Retry Publish does not rerun the AI coding step. It re-attempts review creation from stored branch artifacts.