Code and issues
GitHub
A GitHub integration connects a GitHub App installation to Mobius so loops can react to repository events and call GitHub actions during a run.
Use GitHub when the run needs repository context, issue triage, pull request review, check reporting, or merge operations. GitHub actions can mutate repository state, so keep retrying steps idempotent and add an interaction before destructive changes such as closing or merging a pull request.
Capability map
| Capability | Value |
|---|---|
| Provider ID | github |
| Auth kind | github_app_install |
| Connect flow | GitHub App installation |
| Actions | Yes |
| Events | Yes |
| Webhook delivery | Yes |
| Event samples | Yes |
| Live status | No |
Connect GitHub
| Surface | Support |
|---|---|
| App | Open Govern > Integrations, choose GitHub, and start the GitHub App install flow. |
| CLI | The mobius CLI does not connect GitHub integrations yet. Use the app or API. |
| API | Call POST /v1/projects/{project}/integrations/providers/github/connect, redirect the user to install_url, then let the callback bind the installation. |
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 project.
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.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.repo.get
github.repo.list
github.repo.list_branchesUse read actions first in review loops, then gate write actions with checks or
interactions. Pull request review loops usually read files and comments, produce
a review artifact, then call github.pull_request.create_review.
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.requestedUse github.pull_request.opened or github.pull_request.synchronize for
review loops. Use github.issues.opened for triage loops. Avoid
github.* unless every GitHub delivery should start the loop.
Next
- Build a pull request loop with Review every pull request.
- Build an issue triage loop with Triage GitHub issues.
- Inspect received provider events from source events.