Actions hits six-month GA milestone with new automation features

GitHub Actions became generally available six months ago, and in that span the company has rolled out artifact and dependency caching, self-hosted runners, and an Actions API for extensibility. The team is now highlighting community growth plus several enterprise-focused controls that have landed since launch.

Marketplace and ecosystem growth

The GitHub Marketplace now lists more than 3,200 Actions, a 500% increase in under six months. The recent GitHub Actions Hackathon produced over 700 submissions. Third-party vendors have also expanded deployment options with new Actions from DigitalOcean, Tencent Cloud, HashiCorp, and Docker.

Running runners at the organization level

Organizations can now share and manage self-hosted runners across the whole org using new policies and labels. That allows large teams to centralize management of common infrastructure and keep runner environments consistently configured. Custom runner labels route workflows to specific runner types—for example, compute-intensive jobs can be pinned to virtual machines with eight cores.

Several quality-of-life changes shipped as part of this push:

  • Run defaults let users define shell and working directory settings at the workflow level, which simplifies workflow files and reduces errors.
  • An explicit include matrix gives more control over platform-specific legs of parallel job sets.
  • Job outputs let workflows pass data downstream to subsequent jobs more easily.

Upcoming: secrets management and Enterprise Server support

GitHub is planning additional features aimed at standardizing workflows across organizations for compliance and security, including sharing and managing secrets across multiple repositories, organization-level starter workflows, and advanced continuous deployment capabilities. GitHub Actions and Packages are also in development for GitHub Enterprise Server.