Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add filtering so warning is only given for non-default-selection #663

Merged
merged 1 commit into from
Oct 3, 2024

Conversation

rfbgo
Copy link
Collaborator

@rfbgo rfbgo commented Sep 26, 2024

Previously this would also work for pipelines that don't have phases (eg ramble on). This adds a simple check to only warn if the user requested a change to the phases away from the default path

Copy link
Collaborator

@douglasjacobsen douglasjacobsen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I think this is good. One alternative (I don't really have a strong preference) would be to make whether the pipeline uses phases an attribute of each individual pipeline, and then guard the warning by that.

That would also help catch an (arguably very weird) edge case where an application purposefully removes all of its phases but the phase filter is still ["*"].

Previously this would also work for pipelines that don't have phases (eg
ramble on). This adds a simple check to only warn if the user requested
a change to the phases away from the default path
@douglasjacobsen douglasjacobsen merged commit e41f37e into GoogleCloudPlatform:develop Oct 3, 2024
12 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants