Atmos CI
Configure Atmos native CI integration to automatically update commit statuses, create job summaries, and export plan results inside GitHub Actions.
Atmos has native CI integration that allows it to automatically operate inside GitHub Actions — updating commit statuses, creating job summaries, and exporting plan results. Configure the
ci block in your atmos.yaml to enable these features.ci:
enabled: true
output:
enabled: true
summary:
enabled: true
checks:
enabled: true
context_prefix: ""
statuses:
component: true
add: true
change: true
destroy: trueEach sub-feature controls a specific CI integration:
output— When enabled, exports variables to$GITHUB_OUTPUTso downstream steps in your workflow can reference plan results (e.g., whether changes were detected).summary— When enabled, writes a formatted plan summary to$GITHUB_STEP_SUMMARY, which GitHub renders directly on the workflow run page.checks— When enabled, posts commit status checks to the pull request. Thecontext_prefixlets you namespace the check names, and thestatusesmap controls which check types are reported:componentfor per-component status, andadd,change,destroyfor resource-level operation statuses.
ci.enabled: true also tells Atmos to resolve the right base SHA per event when commands like atmos describe affected need one. Atmos reads GITHUB_EVENT_NAME and GITHUB_EVENT_PATH and picks the correct base for the event:| Event | Base resolution |
|---|---|
pull_request | pull_request.base.sha from the event payload |
pull_request_target | pull_request.base.sha from the event payload |
merge_group | merge_group.base_sha from the event payload |
push | before from the event payload |
So in your Atmos Pro workflows, the affected-stacks step can be as small as
atmos describe affected --upload — no --sha/--ref plumbing. Older templates that pass --sha ${{ github.event.merge_group.base_sha }} or --sha ${{ github.event.pull_request.base.sha }} aren't wrong, just redundant — and they break the moment a new event type is added. See GitHub Merge Queue for the merge-queue context.Next: Configure GitHub Workflows
Create the GitHub Actions workflows that Atmos Pro dispatches to plan, apply, and detect drift on your infrastructure.