Reuse workflow configuration with YAML anchors

GitHub Actions now supports YAML anchors, a top request from the GitHub community. With YAML anchors, you can reuse configuration across your workflows and ensure better conformance with the YAML spec. This feature is automatically enabled for all GitHub Actions users and repositories.

To learn more about how YAML anchors work and see examples, check out the documentation for YAML anchors.

Use workflow templates from non-public .github repositories

GitHub Actions now support workflow templates from a nonpublic GitHub repository. GitHub Actions users can use workflow templates to speed up their development process in their organization by placing templates in a public repository called .github. This repository is also used for other organization templates, like Issue Templates.

GitHub Actions now supports issue templates in nonpublic .github repositories. If the .github repository is internal, then internal and private repositories can use these workflow templates. If the .github repository is private, only private repositories can use these workflow templates. These changes only apply to GitHub Actions — other products that use .github repositories (e.g., GitHub Issues) will continue to only use public .github repositories.

Identify running jobs with job check run ID in GitHub Actions contexts

We’ve added support for the check_run_id value in the job context for GitHub Actions workflows. Now you’ll be able to identify the currently running job directly from within that job by accessing check_run_id. This update makes it easier to handle reporting, send notifications, and upload artifacts that are tied to specific jobs. You can access it inside the job context using job.check_run_id, and it’s available to all GitHub Actions users

Join the discussion within GitHub Community.