Repository navigation
Prevent image publication on branch pushes, including slash names - #148
Merged
Merged
Conversation
sciabarracom
approved these changes
Oct 22, 2026
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.
The image publication workflow excludes branches with
*, which does not match/. Pushing a branch such asfix/0.9.0-monitoring-isolationtherefore unexpectedly starts the image build and registry push workflow.Use
**to exclude every branch name, including names with slashes. Keep the existing tag filter and manual dispatch unchanged. This is a one-line workflow correction, separate from the licensing PRs; it does not change registry credentials or permissions.Validation: parsed the YAML and compared it with the base to verify that only the branch exclusion changes;
git diff --checkpasses. No image publication was requested. Existing branches must incorporate this change before their subsequent pushes are protected by the new filter.