CI

CI runs the workflow files in your repositories on every push, pull request, merge queue build or manual start: native-format workflows and GitHub Actions workflows as they are, on machines the platform creates for a run, on runner pools it starts in your organization, or on Linux machines and Macs you register, with environments, variables, OIDC tokens and required checks.

Get started

  • What is CI?

    CI runs the workflow files in your repositories on every push, pull request, tag or manual start, on machines the platform creates or on machines you own.

  • Getting started

    Add a workflow to a repository, watch its first run and read its log.

  • Workflows and runs

    Where workflow files are read from, what starts a run, where it executes, and the statuses it goes through.

Popular tasks

  • Add a workflow

    Write a workflow file, check it with the same parser a push runs, and commit it to the repository.

  • Run GitHub Actions workflows

    Push a repository with its .github/workflows folder and its workflows run here as they are, with uses actions, matrices, caches and artifacts.

  • Register a runner

    Issue a one-time registration token and register a machine you own as a runner, with GitHub's runner on Linux or by hand on any system.

  • Create a runner pool

    Have the platform start machines in your organization for GitHub-syntax jobs with the pool's labels, one job per machine, and stop them when the work is done.

Operate and secure

  • Security in CI

    Who may read, start, cancel and configure what (IAM), what is audited, and how runs are kept from reaching machines and secrets they should not.

  • Monitoring CI

    Where to see what runs, what waits and why, how your runners and pools are doing, and what CI used.

  • What runs on your machines

    Which machine executes a run, what credentials it holds and for how long, what the runner software on your own machines does, and what happens when something fails.

Guides and references