refactor(rules): Reformat rules with condensed formatting style#544
Merged
rabbitstack merged 1 commit intomasterfrom Dec 26, 2025
Merged
refactor(rules): Reformat rules with condensed formatting style#544rabbitstack merged 1 commit intomasterfrom
rabbitstack merged 1 commit intomasterfrom
Conversation
rabbitstack
force-pushed
the
condensed-rules-formatting
branch
from
09a769c to
11ab687
Compare
rabbitstack
force-pushed
the
condensed-rules-formatting
branch
3 times, most recently
from
96a977c to
57e4337
Compare
Introduce a new rule formatting style for better readability and standardization. Generally, the event type is the first condition in the rule, and almost always appearing as an isolated condition on the first line. All binary operators appear at the end of line, expect the unary not operator.
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
1 participant
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 is the purpose of this PR / why it is needed?
Introduce a new rule formatting style for better
readability and standardization. Generally, the event type is the first condition in the rule, and it almost always appears as an isolated condition on the first line. All binary operators appear at the end of a line, except the unary not operator.
What type of change does this PR introduce?
/kind cleanup
/kind improvement
Any specific area of the project related to this PR?
/area rules
Special notes for the reviewer
Does this PR introduce a user-facing change?