Installation Methods
GitLab
Blazle Anvil scans every merge request on GitLab.com or your own GitLab with the same pipeline and rules as the GitHub App: secrets, planted agent instructions and risky diffs are found before merge.
Before you start
- An Owner or Admin of the BLAZLE workspace.
- A project, group or personal access token with the
apiscope. - Self-managed GitLab must be reachable over https at a public address.
Connect
- Open Integrations in the dashboard, enter your GitLab URL (default
https://gitlab.com) and the token, then Connect. - The webhook URL and secret are shown once. Keep them only if you add a webhook by hand.
- Click Show repositories, then Add webhook on each project to protect.
To add a group webhook by hand, use Merge request events and the secret token shown:
URL: https://api.blazle.io/api/v1/integrations/gitlab/webhook/<WORKSPACE_ID> Secret token: <shown once at connection> (sent as X-Gitlab-Token) Trigger: Merge request events
What happens on a merge request
- On open, reopen and every update with new commits, BLAZLE reads the diff and scans it.
- The result always appears in Intercepts, with GitLab as the source.
- With Scan new changes on, a blocked merge request gets a comment.
- With Hard block on, BLAZLE sets the commit status
BLAZLE Security Scan. Make it required in your merge settings to stop the merge.
Security
The token and webhook secret are encrypted at rest and never shown again. Connecting, disconnecting and adding a webhook are written to the audit log and send a security alert.