Repository navigation
feat(claude): carry an approved plan to prod - #26
Merged
Merged
Conversation
ADR-0029: the merge and release skills fire without a fresh ask for an approved plan's work, and the global instructions say so. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
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.
Follow-up promised by ADR-0029 (fredericrous/decisions#46, v1.0.1). Rebased onto #23 and #25; replaces #24.
work.release-when-the-plan-needs-it).tag-release: the trigger also fires when an approved plan needs the release.merge-when-green: unchanged. feat(skills): merge on green after the push #23's description ("every implementation PR an agent opened") already covers this.Both templates render (
chezmoi execute-template).🤖 Generated with Claude Code