Triggers

Dagger decouples when workflows run from where they run. This page covers triggers — what causes dagger check to run on a git event. Execution is a separate concern, covered in Scaling.

Cloud Checks

The standard trigger is Cloud Checks: a managed service that watches your repository and runs dagger check on every push.

From a local checkout whose origin points to the GitHub repository:

dagger ws autocheck on

If needed, the command guides you through Dagger Cloud signup or login, GitHub authorization, and repository selection. After autocheck is enabled, push code or open a pull request. Checks run automatically and report as commit statuses on your PRs.

No CI configuration files, no webhooks, no runners.

Hybrid mode

If you already have a CI platform and want to evaluate Dagger without replacing it, use your existing CI as the trigger and call dagger check from a job:

# GitHub Actions
- run: dagger check

Because Dagger runs identically everywhere, hybrid mode is a migration bridge — start here, switch to Cloud Checks when ready. Your checks don't change.

Platform-specific setup guides:

• GitHub Actions
• GitLab CI
• CircleCI
• Jenkins
• Azure Pipelines
• AWS CodeBuild
• Argo Workflows
• Tekton
• TeamCity