GitHub
AlphaBase can run inside GitHub Actions to triage issues, review pull requests, and implement changes in isolated branches. This integration currently requires access to the AlphaBase Action repository and an approved release commit. It is not a verified public installation path.
Quick Setup
Obtain the reviewed 40-character Action commit SHA and approved published runtime version from your deployment operator, then run:
export ALPHABASE_GITHUB_ACTION_REF='<reviewed-40-character-commit-sha>'export ALPHABASE_GITHUB_RUNTIME_VERSION='<approved-published-version>'alphabase github installThe installer stops if either value is missing or malformed. It writes a workflow pinned to the supplied Action commit and runtime version. Confirm that your repository’s Actions runner can read both before enabling comment triggers.
Manual Setup
- Install the approved AlphaBase GitHub App on the target repository or organization.
- Generate
.github/workflows/alphabase.ymlwith the installer after setting the reviewed Action commit SHA and approved runtime version. - Review the generated event filters, repository permissions, and action ref.
- Add the required provider key in GitHub Secrets. The default App/OIDC flow does not require a separate GitHub token secret.
The action input model is required. agent is optional. Keep provider
credentials in GitHub Secrets and avoid granting write permissions to untrusted
comment or fork events. A workflow file is an example of integration wiring, not
evidence that the Action or runtime is publicly available.
Session sharing is off by default, including for public repositories. Set the
Action’s share input to "true" only after reviewing the session content and
the deployment’s retention and revocation policy. See Data Handling.
Supported Trigger Patterns
- issue comments
- pull request review comments
- pull request events
- issue events
- scheduled runs
- manual
workflow_dispatch
For non-comment triggers (schedule, issues, pull_request, workflow_dispatch), provide a prompt in workflow inputs.
Security Checklist
- Use least-privilege workflow permissions.
- Keep API keys only in GitHub Secrets.
- Use protected branches and required reviews.
- Restrict which events can write to the repository.
- Use staging repos first before production rollout.
Recommended Operational Pattern
- Start with read-only review tasks.
- Enable write/PR automation after confidence.
- Add scheduled maintenance tasks later (dependency checks, TODO sweeps, docs drift checks).
See Launch Gates and Troubleshooting.