【code format check upgrade】 step3：cpplint #43175
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
|
你的PR提交成功，感谢你对开源项目的贡献! |
betterpig
force-pushed
the
cpplint_upgrade
branch
2 times, most recently
from
fed67f0
to
4d8e5a6
Compare
betterpig
force-pushed
the
cpplint_upgrade
branch
from
4d8e5a6
to
1f9ed5e
Compare
betterpig
changed the title
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.
PR types
Others
PR changes
Others
Describe
upgrade cpplint to 1.6.0, this will not affect the static_check CI result. Because this CI each time use a docker image not installing cpplint, which cause it always install cpplint of default newest version, and that is 1.6.0.
