Connect a GitHub repository
Authorize the MarBoba GitHub app on a repo, wire a project to it, and verify the connection by streaming a PR.
MarBoba talks to GitHub through the MarBoba VCS Connection — a GitHub App + per-org install + per-project repo binding. Once connected, the project’s Code tab shows commits, PRs, and branches in real time, and the AI workflow generator can draft and commit CI/CD workflow YAML directly to the repo.
Prerequisites
- Org admin or Owner role.
- A GitHub repo you can install apps on (i.e. you’re an admin on the GitHub repo, or your GitHub org admin has approved the MarBoba app for org-wide install).
Connect the GitHub App
- Settings → VCS Connections → + Connection.
- Pick GitHub.
- Click Connect on GitHub. You’re sent to GitHub’s app-install flow.
- Choose the GitHub org or personal account, then pick Only select repositories (recommended) or All repositories.
- After approval, GitHub redirects back to MarBoba. The Connections list now shows the install.
Bind a project to a specific repo
- Open the project. Code tab → + Connection → pick the GitHub install you just created → pick the specific repo.
- The Code tab populates: latest commits on each tracked branch, open PRs, build status badges.
Verify
The fastest sanity check:
git checkout -b marboba-smoke-test
echo "smoke" >> README.md
git commit -am "MarBoba smoke test"
git push -u origin marboba-smoke-test
Within ~10 seconds the new branch shows up in the Code tab. Open a PR; it appears in the Pull Requests tab. Merge it; the merge event appears as a deployment trigger (if you have a workflow wired) and contributes to the Velocity dashboard.
Other VCS providers
The same screens work for GitLab, Bitbucket, and Azure DevOps. The underlying connection model is provider-agnostic (read the architecture) — the only thing that changes is which OAuth flow you go through.
| Provider | Connect button | Notes |
|---|---|---|
| GitHub | Connect on GitHub | Most fully tested. |
| GitLab | Connect on GitLab | Self-hosted GitLabs are supported via the base-URL field. |
| Bitbucket | Connect on Bitbucket Cloud | App passwords work; OAuth is preferred. |
| Azure DevOps | Connect on Azure DevOps | PAT-based; org admin must approve the OAuth scope. |
Troubleshooting
- “Connection failed: 401” — the GitHub App’s installation was revoked. Re-run the install flow.
- “No repositories visible” — your GitHub org admin restricted which repos the app sees. Re-run the install and pick All repositories, or have the admin grant the specific repo.
- Workflow YAML commits failing — check that the App has
Contents: Read & writeandPull requests: Read & write. GitHub revokes scopes when the org restricts them; the install page surfaces what’s missing.
See also
- First deploy in 10 minutes — End-to-end path from signup to a green deploy on dev. Assumes you have a GitHub repo and a Stripe-test card.