Integrations
GitHub
Connect repositories so HiveBase can ground coding work in real PRs, Markdown context, and source-linked activity — fail-closed on writeback.
GitHub is a source-first integration for engineering context. HiveBase observes authorized repositories so coding tasks, Squads, and the Brain can ground work in real PRs, issues, and repo docs — not a generic “code vibe.”
Connecting a repo does not mean silent two-way sync of your entire GitHub org, and it does not claim one-shot autonomous coding. Write paths (comments, PR actions, merges) follow the same fail-closed / certification model as other tools: if a path is not live, it does not pretend to be.
What you get
| Capability | Behavior |
|---|---|
| PR & activity signals | Eligible PRs and related activity can surface as context for tasks, FYI, and Engineering squad |
| Repo Markdown context | Selected .md / docs paths can enrich Brain and agent context for planning and verification |
| Task linkage | PRs can be associated with HiveBase tasks so coding work is not free-floating |
| Agent grounding | Connected coding agents (Cursor, Claude Code, Codex, OpenCode) can read company + repo context via MCP — see Agents |
What we do not claim
- No silent full-org two-way real-time sync of every GitHub object.
- No guarantee of one-shot coding success — agents propose; verification and review still matter.
- No automatic merge or force-push without your approval boundaries.
- No replacement of GitHub as the system of record for git history.
Connect GitHub
Open Data Sources
In HiveBase, go to Settings → Integrations → Data Sources.
Connect GitHub
Select Connect GitHub and authorize the GitHub app / OAuth for the account and repos you intend to use.
Pick repositories
Grant only the repos that should ground company context and coding tasks.
Use in work
Open coding tasks or Engineering squad surfaces — context pulls from connected repos and the Brain.
Writeback posture
GitHub writes (comments, labels, merges, branch operations) are only available on paths that are live-certified. Until a path is certified, HiveBase stays fail-closed: it will not silently mutate your repo. Prefer reviewing agent output in GitHub (or your agent host) with HiveBase providing context, receipts, and verification status.
See Trust & safety and the coding task flow on /tasks/code and Coding tasks.
Disconnecting
From Settings → Integrations → Data Sources, disconnect GitHub to revoke access for that connection and stop future ingestion from authorized repos. Existing tasks, source bindings, and Brain claims keep history subject to workspace retention — disconnecting does not silently rewrite the ledger.