Build, test and deploy from your repository
Workflows in GitHub Actions' syntax, run on hosted machines or your own, with live logs, environments, approvals and secrets.
Workflows you already know
A workflow is a YAML file in the repository, in GitHub Actions' syntax. Checkout, cache and artifacts are built in, so workflows from GitHub mostly carry over.
Four ways to start
On a push or a pull request, filtered by branch, tag or path; on a schedule; or by hand, with the inputs you fill in.
Hosted machines or your own
Each hosted job runs on a fresh ARM or x86 machine that's discarded afterwards. Or run jobs on your own Linux, Mac or Windows machines through the agent.
Follow every run
See the jobs as a graph and follow each log as it runs, with search, annotations and summaries. Re-run every job or only the failed ones, or cancel.
Ready for production
Environments and approvals
Required reviewers, a wait timer and the branches that may deploy, before a job reaches an environment.
Secrets and variables
For the organisation, a repository or an environment. Secrets are encrypted, never shown again and hidden in logs.
Matrices and dependencies
A job for each combination, and jobs that wait for others and use their outputs.
Caches and artifacts
Caches per branch, so no branch changes what the default branch restores. Artifacts download from the run.
A status on every commit
Commits, branches and pull requests show whether their runs passed, failed or are still running.
From the terminal
List runs, follow a job's log, re-run, cancel or start a workflow from the command line.
Ship your team's code from Git
Complete and Enterprise include it, with Pipelines, Cloud and the rest of your workplace.