eric sciple 6b03daa25f Prepare to switch GITHUB_ACTION to use ContextName instead of refname (#593)
This PR changes GITHUB_ACTION to use the step ContextName, instead of refname. The behavior is behind a feature flag. Refname is an otherwise deprecated property.

Primary motivation: For composite actions, we need a distinct GITHUB_ACTION for each nested step. This PR adds code to generate a default context name for nested steps.

For nested steps, GITHUB_ACTION will be set to "{ScopeName}.{ContextName}" to ensure no collisions.

A corresponding change will be made on the server so context name is never empty. Generated context names will start with "__".

A follow-up PR is required to avoid tracking "step" context values (outputs/conclusion/result) for generated context names. Waiting on telemetry from the server to confirm it's safe to assume leading "__" is a generate context name.
2021-04-20 21:41:56 -04:00
2021-04-20 21:41:56 -04:00
2021-04-20 21:41:56 -04:00
2019-10-10 00:52:42 -04:00
2019-12-19 15:22:49 -05:00
2019-12-19 09:16:43 -05:00
2020-06-23 14:05:28 -04:00
2020-05-11 15:05:59 -04:00

GitHub Actions Runner

Actions Status

The runner is the application that runs a job from a GitHub Actions workflow. The runner can run on the hosted machine pools or run on self-hosted environments.

Get Started

For more information about installing and using self-hosted runners, see Adding self-hosted runners and Using self-hosted runners in a workflow

Runner releases:

win Pre-reqs | Download

macOS Pre-reqs | Download

linux Pre-reqs | Download

Contribute

We accept contributions in the form of issues and pull requests. Read more here before contributing.

Description
The Runner for GitHub Actions 🚀
Readme MIT 171 MiB
Languages
C# 95.9%
JavaScript 3%
Shell 1%