-
Notifications
You must be signed in to change notification settings - Fork 121
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
Cleanup codebase by running pre-commit. #4253
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Everything under .github
and chrobalt/
and in precommit yaml is fine to land.
However, i didn't expect such a huge churn and diff under /starboard, i think maybe we left some of Pylint / CPPLint config files behind that were previously ignoring a bunch of style diffs ?
Can you bring the config files back and re-run ? That would be .clang-format
at the toplevel and .pylintrc
and .style.yapf
Oh i get it now - we have new |
.clang-format will not be added as Cobalt's .clang-format is a subset of Chromium's .clang-format that will be replacing it at the top level. Cobalt will conform to Chromium's style. .pylintrc will be added at the top level of Chrobalt as Chromium does not use pylint so .pylintrc will only apply to Cobalt. .style.yapf will be added to Cobalt directories as Chromium does use yapf so Chrobalt will avoid any top level changes that will affect Chromium.
cpplint, pylint, and gcheckstyle errors remain.
cpplint and pylint errors remain.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
lgtm now. As it's a large-scale change, worth sending a heads-up for rebase / rerun for everyone after landing it.
There remain 3 pylint "too many positional arguments" failures. These will not be resolved here.
b/371604735