Repository navigation
reconcile --plan-json: write the planned change sets as JSON for chant's change-set document - #66
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
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.
Adds
reconcile --plan-json <file>, which writes the reconcile ChangeSets a run planned (one per cycle and org, a JSON array of chant's@intentius/chant/reconcileChangeSet) without applying anything. It is the file chant'sreadChangeSetPart({ planner: "warden" })reads.runReconcilenow also returns them aschangeSets; combining the flag with--mode applyexits 2.Done when (INTENTIUS/chant#3428): a real warden plan feeds the combined run. This side: the flag and its format. The chant side lands in a follow-up PR.
Part of INTENTIUS/chant#3428