GitHub Actions Preprocessor for Parallel Steps, Workflow Subfolders, and Concurrency Queues

dev tool real project •• multiple requests

GitHub Actions accumulated a long list of 'we've been asking for this for years' features: parallel steps within a job (the Actions team itself calls this 'the most highly requested feature'), subfolders under .github/workflows/ for monorepo organization, dynamic run-name updates, return run_id from workflow_dispatch, queue-multiple-jobs in concurrency groups, and fine-grained tokens for Packages. Third-party composite actions and reusable workflows don't fill these gaps because they're runtime tricks, not workflow-authoring features. Gap: a preprocessor / source language that compiles to stock Actions YAML, giving devs the missing ergonomics today.

builder note

Stay inside the YAML mental model — don't ship a new DSL. Ship extended YAML with `steps_parallel:` blocks, folder-based workflow discovery, and a codegen step that emits stock Actions YAML into `.github/workflows/_generated/`. Market as 'the features GitHub will ship in 2028, today.' Bonus: every feature GitHub eventually adds just becomes a pass-through.

landscape (6 existing solutions)

GitHub is shipping Actions features at a glacial pace for requests that have been open for years. The escape valves (Dagger, Earthly) ask you to rewrite your pipeline in a new language. The unfilled niche is a thin preprocessor: write pseudo-Actions YAML with the missing features, get compiled vanilla Actions YAML out. Same runner, same permissions, better authoring ergonomics.

Composite actions Bundle reusable steps, but can't express parallel-steps-within-a-job. Still one sequential step at the caller level.

Reusable workflows Helpful for reuse, but don't solve subfolder organization or concurrency queue depth > 1.

Dagger Programmable CI pipelines in real languages, but the migration cost is huge — you rewrite workflows in Go/TypeScript. Not a 'fix my Actions YAML' solution.

Earthly Build-focused DSL. Handles parallelism beautifully inside a build, but doesn't replace the Actions scheduling/triggers/permissions model.

act (nektos) Run Actions locally. Doesn't add new features to the spec — it just reproduces the limited one.

DIY YAML anchors + scripts What most monorepo teams do, and it's always fragile. A custom preprocessor is one engineer-year away from becoming an org-wide dependency.

sources (4)

other https://github.com/orgs/community/discussions/181437 "Parallel steps execution... the most highly requested feature" 2026-03-15

other https://github.com/orgs/community/discussions/181437 "Subfolders for managing dozens of workflows in monorepos" 2026-03-15

other https://github.com/orgs/community/discussions/181437 "Fine-grained token support for Packages absent, forcing PAT usage in CI" 2026-03-15

other https://github.blog/changelog/2026-04-02-github-actions-earl... "Early April 2026 updates" 2026-04-02

github-actionsci-cdpreprocessormonorepoworkflow-authoring