feat: scaffold satellite repositories from the game-catalog layout - #3
Merged
Merged
Conversation
game-catalog took a day to get right: a validator that streams instead of loading ~1M records, a site that publishes counts rather than a listing, and a Pages environment that silently rejected main. new_satellite writes that layout from a handful of flags and prints the org-level steps it does not perform. The tests generate a repository and run its own suite and validator, so a template change that breaks generated repos fails here, not in a new repo.
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
1 participant
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.
python -m machine.new_satellite --repo … --category … --title … --plural … [--date-field …] [--range field:low:high] --out …Template = game-catalog's working files with the category turned into placeholders; ranges and date fields are rendered as settings. Writes files only; repo creation, Pages, the
maindeployment-branch rule, and registering the repo inrepos.json/ TechAPISATELLITESare printed as next steps.Tests (18 pass): a generated repo passes its own pytest suite, its validator rejects an out-of-range value and a bad date, no template placeholder survives rendering (Actions
${{ }}excepted), and it refuses to overwrite a non-empty directory.