Powering community-led innovation with GitHub Actions
As we celebrate Actions becoming generally available, check out some of the ways teams are contributing to Actions—and how you can start automating more of your workflow.
As we celebrate Actions becoming generally available, check out some of the ways teams are contributing to Actions—and how you can start automating more of your workflow.
Starting today, GitHub Actions is generally available. GitHub Actions are free for all public repositories and every plan gets included storage and runner minutes for private repositories.
Celebrate a GitHub Action’s milestone with highlights of a few key actions and a technology partner’s work.
The GitHub Actions macOS virtual environment has been upgraded to Catalina (v10.15). Jobs using the `macos-10.14` virtual environment will not run and must be migrated to use `macos-latest`. In addition to Catalina, other changes include: Xcode 11.1 will be set as default Mono 6.4, Xamarin.iOS 13.4, Xamarin.Android 10.0, Xamarin.Mac 6.2 will be set as default .NET Core 3.0 will be set as default…
We’ve fully deployed several updates to the GitHub Actions virtual environments. Highlights include: Ubuntu 16.04 LTS Added newer versions and removed older versions of .NET Core SDK Upgraded Erlang 10.4.4…
GitHub Actions now supports self-hosted runners. Hosting your own runners offers maximum flexibility and control of your workflows. Self-host your runners if you need a proprietary image or container, access…
Self-hosted runners offers a number of advantages when the hosted virtual environments don’t meet all your needs and it’s now available for GitHub Actions in beta.
Using the cache action you can now cache your dependencies between workflow runs. This can dramatically reduce the time it takes to run certain steps in your workflow. The rails/rails…
In order to provide a more reliable experience, we’ve set the minimum time period for scheduled runs to 5 minutes. A schedule of * * * * * which would…
On November 4th, the macOS virtual environment for GitHub Actions will update to Catalina (v10.15), the latest version of macOS X. After the update, jobs using the macos-10.14 virtual environment will…
The Windows Server 2016 virtual environment will be removed from GitHub Actions in January 2020. You will need to update your workflow files to run on windows-latest which will run…
The number of jobs you can run concurrently now depends on your GitHub plan and is shared across all repositories in your account. See Usage Limits for more information.
We’ve fully deployed several updates to the GitHub Actions virtual environments. Highlights include: Windows Server 2016 R2 Added Android SDK Build Tools 29.0.0 and 29.0.2 Added Android SDK Platform 10…
GitHub Actions is changing how we evaluate some events in order to make sure we always run workflows from known refs in your repository. Going forward the following events will…
We’ve fully deployed updates to the GitHub Actions macOS 10.14 virtual environment. Highlights include: Upgraded macOS 10.14.6 (18G95) to 10.14.6 (18G103) Upgraded NVM 12.11.0 to 12.11.1 Upgraded Go 1.13 to…
We will remove Python 3.4 and Ruby 2.3 from all virtual environments in a future update since both reached end-of-life in March 2019.
On 10/23/2019 we will change the default shell for the run step on Windows runners to PowerShell. If your run step contains Windows batch scripting you should update it to…
GitHub Actions are triggered by webhook events. The original payload of the event is stored in a file that actions can read at workflow/event.json (see the docs). We’ve made a…
Check out a few of our favorite GitHub Actions created by our partners at Mabl, Codefresh, GorillaStack, and GitKraken.
The GitHub Actions Marketplace now requires an actions metadata file
We’re sharing examples of productive workflows within the open source community.
Build what’s next on GitHub, the place for anyone from anywhere to build anything.
Get tickets to the 10th anniversary of our global developer event on AI, DevEx, and security.