Repository navigation
feat: read the chant/lifecycle ledger paths and ruleset from the status contract - #64
Merged
Merged
Conversation
…us contract (#62) Add a lifecycle subcommand that reads the branch name and each member's release and gate ledger paths from chant workspace status --json, and prints the ruleset that protects the branch (no deletion, no force push).
5 tasks done
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.
Part of #62.
Adds
github-warden lifecycle. It runschant workspace status <env> --json(contract 1) and reads the branch name fromlifecycle.refand each member's release ledger and gate ledger paths from the document, with nothing hard-coded.--format rulesetprints a ruleset for that branch (rulesdeletionandnon_fast_forward, appends still allowed) in the shape therulesetscycle already reconciles underrepos.<repo>.rulesets. A test loads it through the governance config loader.Acceptance criteria:
chant workspace ls --json(feat: read workspace members from chant's read contract and generate CODEOWNERS #63).chant/lifecyclebranch can be protected by a ruleset.Local checks:
npx tsc --noEmit,npm test(578 passed, with a test against a real chant workspace), the mock smoke,npm run lint:prose, and the CLI run against a temp workspace.