Developer tools
Available now
Halo and GitHub
Connect GitHub to Halo agents through the governed connection catalog.
How Halo works with GitHub
Halo connects GitHub through the Halo connection catalog so configured agents can use permitted repository, pull request, and issue actions.
Actions available through the Halo connection catalog vary by app. Teams can scope access, apply approvals for higher-impact work, and review evidence.
Governance
What Halo governs for GitHub
Scoped repository access
Limit an agent to the GitHub capabilities available for its configured connection.
Approval gates
Require human approval for higher-impact actions under configured policy.
Brokered credentials
Keep app credentials bound at the gateway so agents receive scoped capabilities instead of raw keys.
Reviewable evidence
Record gateway decisions, approvals, and costs for review and export.
Example agent jobs
Put agents to work with GitHub
Illustrative jobs. Each one runs with scoped access, policy, and evidence.
Illustrative pull request brief
For example, a code assistant could prepare a pull request brief using information exposed by its enabled GitHub actions.
Illustrative issue triage
For example, an agent could summarize authorized issue context and draft a next-step note for a person to review.
Setup
Get connected in three steps
- 1
Select GitHub
Open App Connections in Halo and choose GitHub from the catalog.
- 2
Configure repository access
Review the connection flow and available GitHub actions and set the required scope.
- 3
Assign and govern
Attach the connection to an agent, set policy and approval rules, and test the workflow.
FAQ
Questions, answered
The available actions depend on the GitHub connection in Halo’s catalog and the scope configured for it.
Halo brokers app credentials at the gateway so agents use scoped capabilities without receiving raw keys.
Put a halo around the AI your business runs.
See discovery, runtime policy, approvals, and evidence working together on your own use cases.