Skip to main content
A task is a named unit of work you run with aspect <task>: build and test, format, lint, generate BUILD files, deliver artifacts. Tasks that run Bazel add what CI needs on top of it: status checks, PR comments, artifact upload and retries on transient errors. Every task runs the same on your machine and on any CI system. The Aspect CLI ships with the built-in tasks listed below, and you customize them in .aspect/config.axl. You can also add your own: a custom task is an .axl file in .aspect/, discovered automatically and run the same way as a built-in one. Run and define tasks shows how to write one. On Aspect Workflows CI runners, tasks configure Bazel for the runner; see Aspect Workflows runners.
Run aspect help from inside your repo to list every task available, built-in and custom. aspect <task> —help shows a task’s flags with their defaults.

Built-in tasks

Build & test

Formatting & linting

BUILD file generation

Delivery

Affected targets

Agents

CI runners

Setup

Housekeeping

Worktrees

A pool of reusable worktree slots that keep their Bazel output base — and its server — across branches. See the worktrees guide.

Authentication

GitHub App

Discovery commands

These aren’t tasks. aspect help lists them under Commands.

Flags every task accepts

Configure tasks in .aspect/config.axl (AXL), pin the CLI version in .aspect/version.axl (version pinning), and see Running tasks in CI for pipeline YAML for each CI provider.