Support

Connecting GitHub

The /mo signup flow always starts with Slack so Mo can read where your team records decisions. After that, you connect GitHub inside the Mo portal, choose which repositories to watch, then open pull requests as usual—Mo checks each PR’s diff against approved decisions before merge.

This guide SlackSlack → GitHubGitHub · PR checks

1. Finish Slack from /mo first

On the live app, /mo shows the Start using Mo card. The primary action is Start with Slack: the app creates your check session, then sends you through Slack’s install screen so Mo can join your workspace.

Until Slack is authorized, you won’t have the Mo portal project where GitHub is connected. If you haven’t done this yet, follow the full walkthrough on Installing Mo from Slack, then come back here for GitHub.

2. Open the Mo portal and choose Connect GitHub

After Slack install completes, the app keeps you in check mode and lands you in the Mo portal (/mo-portal in the product). The Overview page lists the setup steps; when it’s time to wire up code, use the Connect GitHub control (the same action appears in the Integrations flow).

Clicking it starts GitHub’s OAuth (or token) sign-in with Motionode. Approve the permissions GitHub shows so Mo can read repository metadata, pull requests, and diffs for the repos you select—nothing in this step replaces your normal code review; it lets Mo compare the PR to what Slack says was approved.

Each Mo project uses one git host. If this repository lives on GitHub, connect GitHub here—not GitLab. (Use the GitLab guide if your code is on GitLab instead.)

3. Select repositories Mo should watch

After GitHub is linked, pick the repositories Mo should monitor. Until at least one repo is selected, Mo won’t attach checks to real pull requests.

If your GitHub token expires later, return to the same Integrations / Overview area, reconnect GitHub, and confirm repo selection. You don’t add config files inside the repo for this flow.

4. Open a pull request and read Mo’s results

Work like you already do: push a branch and open a pull request on GitHub—from the link git push prints, or from the repo page via Compare & pull request.

For every new PR on a watched repo, Mo reads the diff and checks it against approved decisions captured from Slack (for example when someone uses @mo to record approval). When something conflicts, Mo surfaces that on the pull request (for example as a comment) so you can fix it before merge.

  1. Slack: Keep deciding in channels; approvals are what Mo compares to.
  2. GitHub: PRs trigger checks automatically—no manual “run Mo” step in the UI.