Skip to content
AlphaBase
HomeDocs

GitLab

Run AlphaBase from GitLab pipelines, issues, and merge requests.

AlphaBase can run in GitLab CI/CD to triage issues, review merge requests, and implement changes through controlled pipeline jobs.

Integration Paths

  • GitLab CI component-based integration
  • GitLab Duo/Agent-style mention-driven workflows

Both approaches run on your GitLab runners.

  1. Store AlphaBase auth/config secrets in GitLab CI/CD variables.
  2. Include an AlphaBase component in .gitlab-ci.yml.
  3. Pass prompt, config directory, and command inputs per job.

Example:

.gitlab-ci.yml
include:
  - component: $CI_SERVER_FQDN/nagyv/gitlab-alphabase/alphabase@2
    inputs:
      config_dir: ${CI_PROJECT_DIR}/alphabase-config
      auth_json: $ALPHABASE_AUTH_JSON
      message: "Review this merge request for regression risks and summarize findings."

Mention-Driven Workflow

Use a trigger phrase in issue/MR comments, for example:

@alphabase review this merge request

The CI job executes AlphaBase with issue/MR context and can post results back to the thread.

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.