We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
There was an error while loading. Please reload this page.
docs(TAM-161): mention tamp init --settings-style=init + per-tool dual-style pointer - Build-Script-Authoring §"Two authoring styles" now points at the new `tamp init --settings-style=init` scaffold flag. - Each per-tool page (NetCli, Docker, Yarn, Vite, Playwright, Turbo, TruffleHog, CodeQL, GraphQLCodegen, Analyzers) gets a uniform "Settings authoring style" section near the bottom pointing back at the side-by-side comparison in Build-Script-Authoring. Fluent stays canonical in every example body — the new section just flags that object-init exists and where to read about it.
docs: refresh for 1.2.0 surface — Internal/Default/CleanArtifacts/object-init - Build-Script-Authoring: anatomy uses 1.1.0+ surface (Internal/Default, CleanArtifacts, no .TopLevel(), object-init authoring style); lifecycle table marks TopLevel() obsolete; Default/Ci shortcuts updated. - Module-Catalog: module-shape example shows both fluent and object-init. - Getting-Started: scaffolded Build.cs uses .Default() and drops the obsolete TopLevel() marker. - Glossary: Internal and Default entries replace TopLevel; Wrapper entry notes the 1.2.0 dual-style overloads. - Migrating-From-NUKE: Unlisted → Internal mapping (renamed in 1.1.0+); migration recipe step 7 updated; .TopLevel() noted as obsolete on upgrade. - Tamp-NetCli: Push target example stripped of .TopLevel(). Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Document DotNet.NuGetPush in Tamp-NetCli reference
Wiki content: build authoring, modules, primitives, CI hosts, migration, FAQ, glossary