Search results for: actions

Workflows triggered by workflow_dispatch and workflow_call can now access their inputs using the inputs context. Previously workflow_dispatch inputs were in the event payload. This made it difficult for workflow authors…

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

You can now enable debug logging when you re-run jobs in a GitHub Actions workflow run. This gives you additional information about the job’s execution and its environment which can…

Actions authors can now specify that their action can run in Node.js 16 by specifying runs.using as node16 in the action’s action.yml. This is in addition to the existing Node.js…

A beta of the Ubuntu 22.04 runner image for GitHub Actions is now available. Start using GitHub Actions to build software on the latest version of Ubuntu by updating your…

GitHub Actions now lets you generate markdown files and publish them as a job summary. We have heard a lot of feedback from users asking for the ability to output…

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

To further reduce the risk of a user using Actions to merge a change into a protected branch that was not reviewed by another person, the organization setting to disallow…

GitHub Actions simplifies using secrets with reusable workflows with the secrets: inherit keyword. Previously when passing secrets to a reusable workflow, you had to pass each secret as a separate…

The macOS 12 Actions runner image public beta is now available. Start using GitHub Actions to build and publish apps for the Apple ecosystem with the latest version of Xcode…

Learn how to build packages with SLSA 3 provenance using GitHub Actions.

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.

If you manage self-hosted runners for GitHub Actions, you can now specify shell scripts that run before the runner starts running a job from a workflow, and after a job…

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

You can now restrict self-hosted runner groups to only be accessible from certain workflows. In addition to restricting which repositories can access specific enterprise and organization runner groups, administrators can…

You can now re-run only failed jobs or an individual job in a GitHub Actions workflow run. For more details see Save time with partial re-runs in GitHub Actions on…

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

Support for Actions in internal repositories is now generally available for GitHub organizations owned by an enterprise account. You can innersource automation by sharing Actions in internal repositories, without publishing…

GitHub code scanning supports a wide variety of code analysis engines through GitHub Actions workflows — including our own CodeQL engine. Users can now discover and configure Actions workflow templates…

In February 2020 we announced the deprecation of the general purpose “Delete reactions” REST API in favor of separate REST APIs for each place reactions can be applied. The old…

Reusable workflows offer a simple and powerful way to avoid copying and pasting workflows across your repositories.