Developer tools
Available now
Halo and GitLab
Govern GitLab agent access through Halo’s connection catalog and gateway controls.
How Halo works with GitLab
Halo connects GitLab through its connection catalog so configured agents can use permitted project, merge request, and pipeline 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 GitLab
Scoped project actions
Configure the GitLab capabilities an agent may use for its assigned workflow.
Approval gates
Require a person to approve higher-impact actions according to configured policy.
Credential brokering
Keep app credentials bound at the gateway and provide agents with scoped capabilities.
Reviewable evidence
Keep gateway decisions, approvals, and costs available for review and export.
Example agent jobs
Put agents to work with GitLab
Illustrative jobs. Each one runs with scoped access, policy, and evidence.
Illustrative merge request summary
For example, a developer assistant could summarize authorized merge request context available through enabled GitLab actions.
Illustrative pipeline handoff
For example, an agent could prepare a pipeline status handoff from information exposed by its configured connection.
Setup
Get connected in three steps
- 1
Select GitLab
Choose GitLab from the app catalog in Halo App Connections.
- 2
Review capabilities
Review the connection setup and scope the GitLab actions needed for the workflow.
- 3
Assign and govern
Attach the connection to an agent, apply policy and approvals, and test the workflow.
FAQ
Questions, answered
Yes. Configured GitLab actions can use scoped access, gateway policy, credential brokering, and approval gates.
No. Actions available through the Halo connection catalog vary by app and configured connection.
Put a halo around the AI your business runs.
See discovery, runtime policy, approvals, and evidence working together on your own use cases.