DocsIntegrations

GitHub

GitHub connects repository work to Mobius.

A GitHub integration connects one GitHub App installation to Mobius. An assistant can read the repositories in that installation, work with issues and pull requests, and respond to repository events.

Use GitHub for issue triage, pull request review, check reporting, or merge operations. The repositories available to Mobius are the ones selected for the GitHub App installation; a Mobius grant cannot expand that upstream scope.

Capability map

CapabilityValue
Provider IDgithub
Auth kindgithub_app_install
Connect flowGitHub App installation
ActionsYes
EventsYes
Webhook deliveryYes
Event samplesYes
Live statusNo

Connect GitHub

SurfaceSupport
AppOpen Build > Integrations, choose GitHub, and start the GitHub App install flow.
CLIThe mobius CLI does not connect GitHub integrations yet. Use the app or API.
APICall POST /v1/integrations/providers/github/connect, redirect the user to install_url. The installation is bound when that same person returns to Mobius signed in.

If the GitHub App was installed but the browser did not return to Mobius, use the installation binding endpoints in the interactive API reference to attach the existing installation to the organization.

GitHub installations use the Account manager choice in Mobius. Choose You for an installation you manage personally or Your team for one organization administrators should manage. After GitHub returns you to Mobius, open the connected account and check GitHub installation for the account and repository scope.

Under Assistant access, grant the exact installation to the assistants that need it. A personal grant limits use of the installation and retention of its tool results to the manager's Mobius audience. For a team-managed installation, choose the team or named people as that audience. If another installation is connected, give each one a clear label so requests and routines can select the intended repositories.

Actions

GitHub registers actions for repositories, issues, pull requests, discussions, checks, commits, releases, and GitHub Actions runs.

github.actions.get_run
github.actions.get_workflow
github.actions.list_jobs
github.actions.list_runs
github.actions.list_workflows
github.check_run.create
github.check_run.list
github.check_suite.list
github.code.search
github.commit.get
github.commit.list
github.commit.set_status
github.discussion.create
github.discussion.create_comment
github.discussion.get
github.discussion.list
github.discussion.list_comments
github.file.get
github.issue.add_labels
github.issue.create
github.issue.create_comment
github.issue.get
github.issue.list
github.issue.list_comments
github.issue.remove_label
github.issue.search
github.pull_request.close
github.pull_request.create
github.pull_request.create_review
github.pull_request.get
github.pull_request.list
github.pull_request.list_files
github.pull_request.list_review_comments
github.pull_request.list_reviews
github.pull_request.merge
github.pull_request.request_reviewers
github.release.get_latest
github.release.list
github.repo.get
github.repo.list
github.repo.list_branches

A pull request review assistant usually reads files and comments, produces a review artifact, then calls github.pull_request.create_review. That write and other GitHub mutations run without an automatic Mobius confirmation after the exact installation and grant are rechecked. For a merge or other change that needs review, use an explicit interaction in the instructions and GitHub branch protection as the enforcement boundary.

Events

GitHub webhook deliveries become provider events with the github. prefix:

github.check_run.completed
github.check_run.created
github.check_run.requested_action
github.check_run.rerequested
github.check_suite.completed
github.check_suite.requested
github.check_suite.rerequested
github.create
github.deployment.created
github.deployment_status.created
github.installation.created
github.installation.deleted
github.installation.suspended
github.installation.unsuspended
github.issue_comment.created
github.issues.assigned
github.issues.closed
github.issues.edited
github.issues.opened
github.pull_request.closed
github.pull_request.edited
github.pull_request.opened
github.pull_request.reopened
github.pull_request.review_requested
github.pull_request.synchronize
github.pull_request_review.dismissed
github.pull_request_review.edited
github.pull_request_review.submitted
github.push
github.workflow_run.completed
github.workflow_run.in_progress
github.workflow_run.requested

Use github.pull_request.opened or github.pull_request.synchronize for review work, and github.issues.opened for triage. Avoid github.* unless every GitHub delivery is worth recording.

Next