GitLab
Organizations with an approved AlphaBase CLI distribution can run it in GitLab CI/CD for controlled review and implementation jobs.
CLI-Driven Job (Recommended)
- Store provider credentials in GitLab CI/CD variables (masked + protected).
- Use an approved versioned CLI distribution in the job image. Public npm availability is not guaranteed.
- Run the resulting
alphabase runcommand non-interactively with the prompt/context for that job.
In a job with the approved CLI already installed, the task command can be:
alphabase run "Review this merge request for regression risks and summarize findings." --format jsonPin the job image and CLI version in your own pipeline. Provision project access through your organization’s approved credential mechanism; do not put a repository token in a clone URL or job log. Review merge request triggers and permissions before allowing write tasks.
Mention-Driven Workflow
Use a trigger phrase in issue/MR comments, for example:
@alphabase review this merge requestA pipeline job triggered by a webhook/bot can parse the comment, then invoke
alphabase run with the relevant issue/MR context and post the result back to
the thread via the GitLab API.
Security Checklist
- Mark sensitive variables as masked and protected.
- Use least-privilege service accounts/tokens.
- Protect default branch and require MR approvals.
- Restrict pipeline permissions for forked contributions.
- Log and retain pipeline audit trails.
Rollout Pattern
- Read-only analysis jobs first.
- Controlled write jobs in staging.
- Production write automation after launch-gate verification.
See Launch Gates and Enterprise.