How
How
How you work with it: getting a command line into existence, the two words the whole model rests on, the file that declares it, where a task body lives, what you see while it runs, and how a version goes out.
This section is wider than installation on purpose. A chapter that explains how the loader reads your manifest is not a reference entry, and calling it one would be a lie about what the page does - so everything that EXPLAINS is here, and With what keeps only what you look a value up in.
Four commands from an empty repository to a working delivery CLI.
The rest of the scaffold: the product name rules, the ignore block, the starter manifest line by line, and shell completion.
A template and a placement of it. Which keys belong to which, and the five things the loader refuses.
The command tree, the group lock, pinning with
with:, aggregates and the product data sections.A body is a plain function. Where it goes, what it may assume, and how it reaches product data.
What you see while a command runs, where its output is kept, and how to ask for the plain version.
One command. Why the tag is the version, why it pushes one tag and not all of them, what the guard refuses - and why a push to
main publishes nothing.