feat: detects push to release branches in cache-poisoning - #352
Merged
Conversation
woodruffw
approved these changes
Dec 23, 2024
woodruffw
left a comment
woodruffw
left a comment
Member
There was a problem hiding this comment.
LGTM, nice work @ubiratansoares!
6 tasks
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.
One more follow-up for #334
We now detect at least one common pattern for Workflows triggered with
push/branches. Deploying when pushing to a convention release branch is quite common, and this change sets the stage to detect other similar branch filters in the future.There is at least one additional PR to before finishing #334, raising it asap!