[K9VULN-9728] Only use production rules for CI checks#797
Merged
jasonforal merged 1 commit intomainfrom Nov 18, 2025
Merged
Conversation
bahar-shah
approved these changes
Nov 18, 2025
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.
What problem are you trying to solve?
Our CI pipeline currently tests rules from staging, which means important tasks like releasing a new analyzer version depend on the state of the staging environment. Because it's acceptable for staging to have half-implemented, mid-edit, or otherwise broken rules, this creates an undesirable coupling.
What is your solution?
Don't run CI against staging rules
Alternatives considered
What the reviewer should know