update fluent-operator to v3.2.0 #553
Merged
Conversation
This file contains 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
reegnz
requested review from
benjaminhuo,
wanjunlei and
wenchajun
as code owners
Signed-off-by: Zoltán Reegn <zoltan.reegn@gmail.com>
reegnz
force-pushed
the
update_fluent-operator_to_3.2.0
branch
from
19723b1
to
e887b0b
Compare
|
Thanks，please modify it |
|
@wenchajun just copied from upstream verbatim (fluent/fluent-operator). Maybe these linter rules should also run there. |
Yes, there is a bit of a difference between the two for formatting, so you need to crop accordingly. |
Signed-off-by: Zoltán Reegn <zoltan.reegn@gmail.com>
reegnz
force-pushed
the
update_fluent-operator_to_3.2.0
branch
from
9aea2cb
to
2e20c4a
Compare
|
Fixed linter errors. |
wenchajun
approved these changes
Sep 24, 2024
|
thanks |
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.
No description provided.