Search results for: GitHub Actions

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.

We’ve fully deployed updates to the GitHub Actions macOS 10.14 virtual environment: Added Java 13 Upgraded NVM 12.10.0 to 12.11.0 Upgraded CocoaPods 1.7.5 to 1.8.0 Upgraded Azure CLI 2.0.72 to…

GitHub Actions has new settings for organizations and repository owners to limit the usage of external Actions.

Users and organizations who register for the GitHub Actions and GitHub Package Registry betas are now automatically granted access.

It’s now even easier to create and edit a GitHub Actions workflow with the updated editor. We’ve provided inline auto-complete and lint as you type so you can say goodbye…

Edit your GitHub Actions workflow files easier with features to help you minimize errors and more.

We have stopped running HCL workflows, as announced on the 17th. If you still have HCL workflows, please convert your `.github/main.workflow` files using the migrate tool.

The GitHub Actions workflow syntax has new features based on feedback from our community. Env at the workflow and job level It is common to need define a set of…

GitHub Actions is built on top of webhooks and checks and uses the CheckSuiteEvent for re-running workflows.  Using the CheckSuiteEvent for re-run can lead to non-deterministic results due to the…

We’ve updated the event filtering syntax for paths, branches and tags to better support common scenarios and address some customer feedback. In the initial syntax it was not possible to…

We’ve fully deployed several updates to the GitHub Actions virtual environments. Ubuntu 16.04 LTS Upgraded Ansible 2.8.4 to 2.8.5 Upgraded Azure CLI 2.0.71 to 2.0.73 Upgraded AWS CLI 1.16.221 to…

GitHub Actions uses the Checks API for representing and storing information about job executions. These checks appear in many places in the GitHub UI such as the merge box of…

GitHub Actions runner has been updated to version 2.158.0 with the following improvements: Support for Alpine based containers in job.<job id>.container andjob.<job id>.services. Stop overriding the working directory for job.<job id>.services containers.…

On September 30, 2019, GitHub Actions will stop running workflows written in HCL. You’ll need to migrate your HCL workflows to the new YAML syntax using the migration script.

Since we introduced GitHub Actions last year, the response has been phenomenal, and developers have created thousands of inspired workflows. But we’ve also heard clear feedback from almost everyone: you want CI/CD! And that’s what we’re announcing today.