5c49625758
The upcoming DAP execution-view renderer serves a synthesized YAML document as the job's debugger source. The skeleton is hand-emitted so we can track per-step line offsets, but scalar values (step names, action refs, etc.) need quote-safe formatting that respects YAML's reserved chars, leading/trailing whitespace, and embedded `: `/`#` sequences. Doing this by hand is bug-prone and easy to get wrong on edge cases (empty strings, expressions, multiline content). This commit adds a thin wrapper around YamlDotNet's `Emitter` that emits a single scalar, strips the surrounding document markers, and forces LF line breaks (`StringWriter` otherwise picks up Windows's CRLF via `Environment.NewLine` and corrupts the document-end stripping). No caller yet — the renderer that uses it lands in a follow-up PR. This is part 1 of 5 splitting the previously-monolithic foundation for review tractability. 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.