Skip to content

GitLab

Organizations with an approved AlphaBase CLI distribution can run it in GitLab CI/CD for controlled review and implementation jobs.

  1. Store provider credentials in GitLab CI/CD variables (masked + protected).
  2. Use an approved versioned CLI distribution in the job image. Public npm availability is not guaranteed.
  3. Run the resulting alphabase run command non-interactively with the prompt/context for that job.

In a job with the approved CLI already installed, the task command can be:

Terminal window
alphabase run "Review this merge request for regression risks and summarize findings." --format json

Pin 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 request

A 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

  1. Mark sensitive variables as masked and protected.
  2. Use least-privilege service accounts/tokens.
  3. Protect default branch and require MR approvals.
  4. Restrict pipeline permissions for forked contributions.
  5. Log and retain pipeline audit trails.

Rollout Pattern

  1. Read-only analysis jobs first.
  2. Controlled write jobs in staging.
  3. Production write automation after launch-gate verification.

See Launch Gates and Enterprise.