Run Recipes
Run all registered recipes in sequence.
Summary
The run-recipes command discovers and executes all registered recipes in sequence. This is the single command that replaces chaining individual recipe commands.
There is no category flag, so every invocation runs all recipes across the github, license, miscellaneous, read-me, and package-json categories.
Recipes reconcile settings or existing content and are safe to run again. They do not invoke generators; generated files remain an explicit nova generate ... action.
Recipe Categories
| Category | Recipes |
|---|---|
github | sync-actions, sync-features, sync-identity, sync-labels, sync-policies, sync-rulesets, sync-security |
license | update-copyright |
miscellaneous | fix-markdown-tables |
read-me | update-badges, update-credits, update-documentation, update-header, update-introduction |
package-json | sync-identity, sync-ownership, normalize-modules, normalize-artifacts, sync-environment, normalize-dependencies, normalize-bundler, normalize-tooling, cleanup |
Why Use This Command?
- One command to rule them all — Instead of chaining
nova recipe package-json sync-identity && nova recipe package-json sync-ownership && ..., run a singlenova utility run-recipes. - Consistent ordering — Recipes execute in their registered order, ensuring dependencies between recipes are respected.
Requirements
- Node.js runtime — Use any Node.js LTS release with either the installed
novaCLI ornpx. nova.config.json— A validnova.config.jsonfile must exist at the project root with configured workspaces.
Usage
Options
| Flag | Description |
|---|---|
-d, --dry-run | Preview file and GitHub changes without sending mutations. |
-r, --replace-file | Overwrite the original file instead of creating a .nova-backup copy. |