Validation gates each task in a run. Coder does not claim a task done until its checks pass.
What is checked
- Type checks*: the project's type checker must pass.
- Tests*: the relevant test suite must pass.
- Security checks*: the changes are scanned for common security issues.
- Lint/format*: project style and lint rules are respected where configured.
How gates work
Each task has a success check. If a gate fails, the task is reported as failed with the output attached, and the run does not silently mark it complete. You fix the issue or adjust the queue, then continue.
Local vs cloud
Validation runs in the same workspace the task ran in — locally on your machine or in the cloud workspace for a cloud run. The checks and their results are recorded on the run record either way.
Honest completion
Coder is built to run the project's own checks rather than assume success. A task is only marked done when the checks it can run actually pass; if a check cannot run, that is reported rather than hidden.
Related
- Tasks are produced by the [task queue](/docs/coder-task-queues).
- Output is produced through your [Git workflow](/docs/coder-git).
Was this article helpful?