Repository navigation
Categorize Foundry commands and document workspace workflows - #7
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Foundry's flat command list made it difficult to tell which generators belong to Go or Flutter, and which development commands must run in a generated workspace. Group CLI help into discovery, creation, Go scaffolding, Flutter scaffolding, maintenance, and native project development.
Add a workspace guide covering root identification, command applicability,
--projectbehavior, and creation-to-validation workflows for all five templates. Document explicit app selection for Flutter, the absence of web/Rust scaffolding generators, and the difference between Foundry-repository and generated-project tasks. Link the guide from the README/reference and include workspace-specific guidance in every generated README.Validation
make ci: formatting, vet, tests, build, and smoke generation for all five templates passed.npm run format:check.foundry helpandfoundry add --help; root/guide relative links andgit diff --checkpassed.