Skip to main content
The GitHub App is how Momentic reads and writes back to your repository: Mo sessions on pull requests, test status comments, auto-heal repair PRs, and AI routing for where a repair lands. Mo and regression tests use the same installation.

What the app does

Install

  1. Open Settings > Integrations in the dashboard.
  2. Click Connect on the GitHub card and authorize Momentic to check which installations your GitHub account can access.
  3. Pick an existing installation, or choose Install on another account and select either All repositories or a subset in GitHub.
The same GitHub App installation can be linked to multiple Momentic workspaces. This is useful when those workspaces use repositories from the same GitHub organization. To reuse an installation, you must be able to manage integrations in both the workspace that already uses it and the workspace you are connecting. Each Momentic workspace still connects to only one installation. Status comments are on by default once the app is installed. Configure them with Comment on in the GitHub section of Settings > Notifications.

Pull request comments

Comment on controls what Momentic posts on the pull request for a branch:
  • Off posts no status comment.
  • Failures and repairs comments when tests fail, warn, or are repaired, and removes the comment once every run group for the commit has been evaluated and is clean. A failing or still-running group keeps the comment in place.
  • All runs also keeps a comment when every test passes. With Result format set to Test details, that comment is compact.
Result format on the same page picks what a comment shows: Test details lists links and repair notes for up to four tests, and Run groups shows run group summaries. Larger results always use run groups. The setting also applies to Slack messages.

Data flow

How a run becomes a PR comment:
The comment links each run back to the dashboard’s video, trace, and step evidence. New runs on the same branch edit the existing comment rather than posting a new one. Healing goes the other direction: ai triage writes repaired test files, then opens a PR through the app. AI routing decides the target: a commit on the branch under test when the branch caused the failure, a separate PR against gitMainBranch when it did not, or a reference to an existing PR when the fix already exists.

Permissions

The app requests repository permissions at install time. Two are worth knowing:
  • Issues or pull requests: write: required for the status comment. If a reviewer approved the app with a reduced permission set, comments silently skip.
  • Contents: write: required for healing PRs and AI-routed commits. Without it, triage still analyzes but cannot deliver a PR.
When Momentic ships a feature that needs a new scope, GitHub emails the org admins a “new permissions” request. The capability stays off until an admin approves it in GitHub; the request does not appear in Momentic settings.

Gotchas

  • Subset installs. If you installed on selected repositories, PRs in other repos get no comment and heals cannot push there. Update the repo list on the installation’s GitHub page (org Settings > GitHub Apps > Momentic > Configure).
  • Forks. Runs triggered on fork PRs comment on the upstream PR only when the app is installed on the upstream repo: the normal case. Runs inside the fork’s own repo need the app installed on the fork.
  • Renames and transfers. Repository renames are followed by GitHub, but a repo transferred to a different org leaves the installation. Reinstall under the new org.
  • One installation per workspace. A Momentic workspace can connect to one GitHub App installation. Disconnect the current installation before linking a different one.

Uninstall or disconnect

  • From Momentic: disconnect on the GitHub card in Settings > Integrations. If other Momentic workspaces share the installation, this unlinks only the current workspace. Otherwise, it also uninstalls the GitHub App, preserving the behavior of an unshared connection.
  • From GitHub: uninstall the Momentic app under the org’s Settings > GitHub Apps (or Settings > Applications for a personal install). The installation.deleted webhook marks the Momentic side disconnected automatically.

Mo on pull requests

Connect GitHub to give Mo repository context, start pull request (PR) sessions from the web composer, comments, labels, or the CLI, and receive reports and commit checks. Reports include findings and playback links for selected verified flows when recordings are available.

Connect GitHub

Install the Momentic GitHub App in Settings > Integrations. Connect your personal GitHub account in Settings > Profile to start sessions through comments or labels. You must belong to exactly one Momentic workspace connected to that installation; otherwise, start in the intended workspace. Workspace access and billing limits apply.

Add repository context

Select repositories on the Mo workspace page for read-only code and diffs. Include a repository or PR reference and your app’s URL in your brief. See workspace repositories for refresh behavior and revision checks.

Start a PR session

From the web app

Paste a GitHub PR link into your description. The selected PR appears as a GitHub pill. Include the app URL in your description when known; see Choose a preview for what happens without one.

From a comment

Mention Mo in a new comment on an open PR:
Mo acknowledges the request with an eyes reaction and posts a session link when testing starts. Open that link to answer access and testing questions. Questions, incidental mentions, edits, and inline review comments don’t trigger sessions.

From a label

  1. Set Trigger label under Label trigger in Settings > Run settings (Settings > Triggers in some workspaces).
  2. Optionally set Environment under Label trigger. The default, Automatic, uses an environment that matches the PR context, or an available PR preview.
  3. Apply the label to the PR. The person adding it must connect GitHub in Settings > Profile.
Mo tests the captured commit, skipping changes without testable app behavior. Remove and reapply the label for another run; removing it or pushing commits doesn’t cancel or restart testing. Clear Trigger label to disable label triggers.

From the CLI

Start a session against the PR’s deployment:

Choose a preview

How Mo finds the target depends on how the session starts:
  • Web app, PR API, qa start --pr, or MCP: pass the app URL, previewUrl, or --url. Otherwise Mo checks the PR’s head commit once for Vercel, Cloudflare Pages, or Netlify preview links. If it finds none, the start fails with “No preview was found for this PR commit”; add the URL and retry. A Momentic environment does not skip this check. See qa start options for unpublished patches.
  • Comment or label: a URL in the brief or a selected environment skips discovery. If Mo finds no preview, the session still starts, and Mo inspects the PR or asks you which app to test.

Review results

PR sessions show a PR badge. Each session updates its review with findings, agent counts, runtime, and up to three verified-flow recordings. Earlier reviews collapse as Outdated. Copy for your coding agent includes bug summaries and available source diagnoses. Open the report for evidence.

Commit checks

With Checks access, the Mo check follows the latest request on that commit. Common results: The check doesn’t verify the deployed revision. With Pull requests: write, Mo posts reviews; with Issues: write alone, it posts PR comments.