One repository. A clear view of what will collide.
- Sign up or log in with GitHub, Google or email, and open the right Merget organization. An organization owner connects the GitHub App; GitHub must also let that person install or administer it.
- In Merget, open Settings › GitHub and choose Add GitHub organization. Personal GitHub accounts work too.
- On GitHub, choose Only select repositories, pick your first repository, review the permissions, and install.
- Return to Merget and enable the repository. Newly connected repositories start disabled and in Advisory mode.
- Review findings on your open pull requests. Configure checks and reviews before moving to Queue or Autonomous.
Merget supports public and private repositories on GitHub.com. GitHub Enterprise Server, other GitHub domains, GitLab and Bitbucket are not supported today.
Start with findings. Add resolution when you are ready.
Advisory
Analyzes pull requests and suggests an order. It posts checks and comments, but changes no source code or branches and makes no model requests. A blocking finding can fail a required Merget check. With Administration access, Merget may rename a legacy required check from sema to Merget.
Queue
Also resolves conflicts and publishes prepared fixes when needed. You choose when to merge, in GitHub or through an offered dashboard action.
Autonomous
Also starts ready merges automatically under the repository’s configured requirements. Required checks and reviews apply by default; explicit overrides and push-based batch landing need a deliberate policy review.
Compare the modes and read the landing controls before enabling writes. Pull Merget’s commits before pushing more work to a branch it has updated.
Know what Merget can access before you install.
| Permission | Access | Purpose |
|---|---|---|
| Checks | Read and write | Posts the Merget check and reads other check results. |
| Pull requests | Read and write | Reads PRs and posts review comments. Queue and Autonomous can resolve Merget’s own obsolete review threads and retarget stacks; Autonomous can merge. |
| Contents | Read and write | Reads code for analysis and optional builds. Writes in Queue and Autonomous publish fixes, manage temporary branches and land batches. |
| Administration | Read and write | Reads protections and rulesets; can turn off strict up-to-date protection after an owner confirms. May rename the legacy required sema check in every mode. With Actions access, reads repository runner availability after observing batch jobs. |
| Actions | Write, when granted | Cancels obsolete batch workflow runs when configured. Read access supplies batch job timing; without it, Merget reads check runs. |
| Workflows | Write, when granted | Lands a PR’s own workflow change when merging it creates workflow content not already on your branches. Merget’s fixes do not edit workflow files, and fork workflow changes need a person to merge. |
| Commit statuses | Read | Reads CI results reported as commit statuses. |
| Metadata | Read | Reads basic repository information required by GitHub Apps. |
| Members (organization) | Read | Reads organization and team membership, including teams named in CODEOWNERS when Merget checks code-owner review. |
You choose the repositories the App can access. Private build dependencies need a separate explicit grant; selecting all repositories does not grant dependency access by itself.
Disabling a repository stops new Merget work but retains its settings and data. Uninstall the App on GitHub to revoke its GitHub access. Read about data and security.
Choose the landing path deliberately.
By default Merget lands through GitHub’s merge path, where your required checks and reviews apply. Authorized users can explicitly override a blocked merge, and Autonomous repositories can opt into landing on Merget’s verdict.
A fast-forward push requires the App to have bypass access. On that path Merget checks approvals, code-owner review, latest-push approval, resolved review threads and required checks itself.
On a bypass push, Merget does not evaluate file-specific required reviewers, required deployments or workflows, code scanning, or commit and file restrictions. Keep these rules outside the App’s bypass scope or use GitHub’s merge path. A fix held in the combined queue result can land in a batch without appearing on a reviewed pull request head.
If a branch uses GitHub’s native merge queue, Merget still prepares pull requests and you merge through GitHub’s queue. Read about security and controls.
Code analysis for ten languages. Textual conflicts in every repository.
| Language | Extensions |
|---|---|
| C | .c, .h |
| C# | .cs |
| Go | .go |
| Java | .java |
| JavaScript | .js, .jsx, .mjs, .cjs |
| Kotlin | .kt, .kts |
| Python | .py |
| Rust | .rs |
| Scala | .scala, .sc |
| TypeScript | .ts, .tsx |
Extension matching ignores case. C++ is not included; .h files are read as C. Extensions such as .mts, .cts, .pyi, .pyw and .csx are not covered.
Coverage varies by language and construct. Cross-language calls, dynamic behavior and build-specific C headers can limit analysis. Argument-count checks do not cover every type incompatibility. Generated or minified files receive no code findings. Use each run’s Coverage report alongside your CI and review.
Unsupported files still enter the queue and receive textual-conflict reporting; your CI can verify their fixes.
Bring your agent. Give it the queue’s context.
Claude Code, Codex, GitHub Copilot, Cursor, Devin, Kiro and Google Antigravity can use the Merget plugin. Other clients that support remote MCP, including Replit Agent, can connect to the same service.
The Merget plugin bundles the MCP server and skills. For a client without plugins, connect its remote MCP settings to https://sema.merget.ai/mcp. Use one connection path to avoid duplicate tools.
You sign in through the browser and approve an organization and permissions. Agents act through your access; organization and repository controls can restrict them. They cannot grant themselves ownership or expand their own permissions.
To set up an agent in one step, paste this into it:
Fetch and execute the instructions to set me up for Merget from https://sema.merget.ai/agent-setup/prompt.mdReview pricing, sign up free, or read the Markdown version of these docs.