Remove feature branch from publish workflow triggers - #57
Merged
Conversation
The branch trigger was only needed for the pre-merge CI dry-run; the deploy step stays gated to dev. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GXdH68Zgh99MDTF5Cpkn7q
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
2 participants
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.
Post-merge cleanup for #56: the feature branch was in the workflow's push triggers only to validate the render pipeline on CI before switching over. Now that the migration is merged and deployed, restrict the trigger back to
dev. Theif: github.ref == 'refs/heads/dev'gate on the deploy step stays as a safety measure.🤖 Generated with Claude Code
https://claude.ai/code/session_01GXdH68Zgh99MDTF5Cpkn7q
Generated by Claude Code