Skip to content
Registry StackDocsv0.46.0

bregctl examples review command reference

View as Markdown

Create and connect fresh facility and canonical Casework development projects.

This page is generated from the public Clap command tree for Registry Stack source version 0.46.0 and catalog SHA-256 d43b1bf418e0b00fac52311fa3a106fa124512dbc88cf511475713af2d73aa47. Hidden implementation commands are omitted.

bregctl examples review [OPTIONS] <DIRECTORY>
ArgumentAlways requiredDefaultValuesEnvironmentDescription
<DIRECTORY>Yesn/an/an/aFresh destination for the facility and canonical Casework projects. A symbolic link at any component of this path is refused.
OptionAlways requiredDefaultValuesEnvironmentDescription
--approveNon/an/an/aExplicitly record approval as the local synthetic Casework staff fixture. The decision uses Casework’s ordinary claim, context and decision APIs
--caseworkctl-bin <CASEWORKCTL_BIN>Non/an/an/aCasework authoring CLI from the same installation
--casework-bin <CASEWORK_BIN>Non/an/an/aCasework runtime executable; otherwise resolve casework on PATH
--breg-bin <BREG_BIN>Non/an/an/aBase Registry Engine (BReg) runtime executable; otherwise resolve breg on PATH
--format <FORMAT>Nohumanhuman, jsonn/aEmit the selected command’s report in this format
-h, --helpNon/an/an/aPrint help

After changing a public command, argument, option, default, environment binding, or help description, run cargo run --locked -p registry-cli-docs -- --write, commit crates/registry-cli-docs/catalog.json, then run npm run generate from docs/site.