9f41c09ca4
Bridges the runner's IStep / IActionRunner types to the renderer's
JobExecutionViewEntry (#PR1b). Given a runtime step, produces the
data the renderer needs to emit one entry in the execution view.
Specifically:
- Determines the entry's phase from ActionRunStage / IStep type.
- Filters JobExtensionRunner and other non-IActionRunner steps:
those represent runner-internal scaffolding, not user-visible
steps.
- Filters auto-generated step IDs (regex against `^__\d+$` and
GUID-shaped strings) so only explicit `id:` fields surface.
- Serializes `with:` and `env:` via TemplateTokenYamlAdapter
(#PR1d) so `${{ ... }}` expressions are preserved verbatim in
the rendered source.
- Extracts `run:`, `shell:`, `working-directory:` from a script
step's `Inputs` map using the constants defined in
PipelineConstants.ScriptStepInputs (the runner stores these as
camelCase `workingDirectory`, not the kebab-case spelling from
workflow YAML).
This is part 5 of 5 splitting the previously-monolithic foundation.
The DAP-integration PR wires this into JobRunner / ExecutionContext
so steps actually flow into the execution view at runtime.
Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>
GitHub Actions Runner
The runner is the application that runs a job from a GitHub Actions workflow. It is used by GitHub Actions in the hosted virtual environments, or you can self-host the runner in your own environment.
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:
Note
Thank you for your interest in this GitHub repo, however, right now we are not taking contributions.
We continue to focus our resources on strategic areas that help our customers be successful while making developers' lives easier. While GitHub Actions remains a key part of this vision, we are allocating resources towards other areas of Actions and are not taking contributions to this repository at this time. The GitHub public roadmap is the best place to follow along for any updates on features we’re working on and what stage they’re in.
We are taking the following steps to better direct requests related to GitHub Actions, including:
-
We will be directing questions and support requests to our Community Discussions area
-
High Priority bugs can be reported through Community Discussions or you can report these to our support team https://support.github.com/contact/bug-report.
-
Security Issues should be handled as per our SECURITY.md
We will still provide security updates for this project and fix major breaking changes during this time.
You are welcome to still raise bugs in this repo.