Skip to content

Add Dialects to rootform.lock.

Usage

rootform add dialects <source>... [options]
SHELL

Options

FlagTypeDefaultDescription
--dry-runboolfalseprint the planned change and write nothing
--formatstring""output format: text|json; default: text
--offlineboolfalseuse no network; accept local and installed sources
--projectstring""change rootform.lock and vendored copies in project dir; paths stay relative to the working directory; default: the working directory
--replaceboolfalsereplace the embedded Dialect with the same owner

Global options

FlagTypeDefaultDescription
-h, --helpboolfalseshow how to use rootform add dialects
--colormodeautocolor human output: auto|always|never; default: auto
--no-pagerboolfalseprint a long report in full instead of opening it in less

Behavior

Add Dialects to rootform.lock. Each source is a local directory (./path), a registry reference with a tag or digest, or the owner of an embedded Dialect that the project excluded.

Rootform compiles and verifies every source, records its exact identity, and writes rootform.lock once, or not at all. A registry source is installed in the Rootform home. A tag is resolved once and never recorded.

A Dialect whose owner is embedded in Rootform replaces the embedded one only with --replace.

When the project vendors this family under .rootform/, the vendored copy changes together with rootform.lock.

The summary goes to standard output. Diagnostics go to standard error.

Exit status

StatusDescription
0rootform.lock matches the request
1a source is invalid or a named selection is absent
2the command was used incorrectly
3rootform.lock is invalid, selections conflict, or --offline needs content that is not installed
4a file, Rootform home, or network operation failed

Examples

rootform add dialects ./dialects/payments
rootform add dialects \
registry.example.com/acme/dialects:dialect-payments-0.1.0
rootform add dialects ./dialects/aws --replace
Shell