GitHub Actions

The GitHub Actions team has done lots of work to improve the performance and resource consumption of Actions on GHES in the past year.

Now your team can spend less time managing infrastructure and more time writing code.

As GitHub Pages, home to 16 million websites, approaches its 15th anniversary, we’re excited to announce that all sites now build and deploy with GitHub Actions.

GitHub Actions gives teams access to powerful, native CI/CD capabilities right next to their code hosted in GitHub. Starting today, GitHub will send a Dependabot alert for vulnerable GitHub Actions, making it even easier to stay up to date and fix security vulnerabilities in your actions workflows.

New Actions from Anchore, NowSecure, SBT, and Trivy are now available to create a more comprehensive GitHub Dependency Graph.

Can projects and GitHub Actions be used by your non-developer teams? They absolutely can. Check out how our Security Team uses GitHub to run the department effortlessly.

CI/CD and workflow automation are native capabilities on GitHub platform. Here’s how to start using them and speed up your workflows.

Several ways for GitHub-hosted Actions runners to connect to resources on your private network.

GitHub Enterprise Server 3.5 is available now, including access to the Container registry, the addition of Dependabot, enhanced administrator capabilities, and features for GitHub Advanced Security.

You can now output and group custom Markdown content on the Actions run summary page.

From plug-and-play automations to protected branches, here are simple ways any developer can build more secure software on GitHub—all with a free account.

The new dependency review action and API prevents the introduction of known supply chain vulnerabilities into your code.

From automating builds and releases to taking care of large-scale regression testing, here are a few ways we use GitHub Actions to build GitHub.

You can now enforce consistent usage of self-hosted runner groups across your organization and enterprise.

It is now possible to re-run only failed jobs or a single job in GitHub Actions workflows.