Set up Cloud Checks
In this guide, you will connect your GitHub repository to Dagger Cloud, and run your Checks automatically after each push.
Complete the Quickstart before you start.
A Git event, such as a push or pull request, starts Cloud Checks. They run your Checks on Cloud Engines. You do not need a CI workflow file.
Your project must be a GitHub repository, and its Git origin remote must point to that repository.
Enable Cloud Checks
From your project root:
dagger cloud checks on
Dagger gets the repository from the Git origin remote. The command prints on when Cloud Checks are enabled. If they are already enabled, it makes no change.
In an interactive terminal, the command offers to complete missing prerequisites:
- Sign in or create a Dagger Cloud account and organization.
- Connect the GitHub account or organization that owns the repository. In the browser, grant Dagger access to the repository.
Each prerequisite must finish before the command enables Cloud Checks. You can decline a prompt and complete it later.
In non-interactive mode, the command stops and prints the required command followed by the command to retry. It does not open a browser or wait for input.
You can also complete the prerequisites separately:
dagger cloud signup
dagger cloud integration create github --open
Complete the browser steps, then retry:
dagger cloud checks on
Trigger Cloud Checks
Commit the files that the Quickstart created, then push them:
git add dagger.toml
git commit -m "Set up Dagger"
git push -u origin HEAD
If dagger generate changed other files, stage those too. Run git status --short to list them.
Watch the Checks pass
The push started your Checks. Watch them run:
dagger activity
Find the row for Set up Dagger. It can take a moment to appear. Run the command again until its CHECKS column is green.
If a Check turns red, run dagger check locally. Fix the failure. Then commit and push the fix.
Green means that every Check passed.
What you accomplished
Your project now checks itself. Every push and every pull request runs your Checks automatically, on Dagger's Cloud Engines.
You did not write a CI workflow file. You do not maintain a build server. The Checks that run on each push are the same Checks that dagger check runs on your machine, so the two cannot drift apart.