Extract env declarations from a GitHub Actions workflow without sending the file to a server. The report keeps workflow, job, and step context, identifies expression-backed values, and highlights later declarations that shadow the same variable name.
An indentation-aware scanner finds env mapping blocks and associates each entry with the nearest workflow, job, or step context.
Quoted values are unwrapped for display. Multiline YAML scalars and env objects created through anchors require a full YAML parser and are reported as limitations.
Try the sample input built into the page. The result uses the same validation and export path as pasted content.
name: CI
env:
NODE_ENV: test
API_BASE: https://example.test
jobs:
build:
runs-on: ubuntu-latest
env:
NODE_VERSION: "22"
steps:
- run: npm test
env:
CI: trueThe extractor ignores comments and scans conventional block-style workflow YAML. It records line numbers for each declaration.
Flow mappings such as env: {A: 1} and complex YAML anchors are not expanded.
Use the format shown in the sample. The page validates required fields and reports malformed lines or values before producing output.
No. Processing happens in your browser and the core function makes no network request.
Yes, after reviewing repository-specific names, permissions, paths, and policies that a browser-only tool cannot verify.
Hosted services may apply repository context, current platform rules, presets, or permissions that are unavailable to this local check.
Yes. The input and downloaded files use UTF-8, although the target format may impose narrower naming or syntax rules.
| Item | Meaning |
|---|---|
| Output | Copy-ready JSON or text |
| Processing | Local browser execution |
| Network | Not required |
Browse generators, parsers, validators, and helpers for Git configuration and repository workflows.
View category