-
Notifications
You must be signed in to change notification settings - Fork 534
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
Use Buildifier with Bazel #3000
Comments
Per @adhiamboperes's suggestion this has been completed. I'm actually not sure what it wasn't closed a while back since we've been running buildifier in CI for a few years now (and locally after running the scripts/setup.sh script). Buildifier integration will also get better integrated in an upcoming Bazel PR along with all other static script checks. |
The issue is reopened because of the following unresolved TODOs: oppia-android/scripts/pre-push.sh Line 16 in d0c8b81
|
Aha, looks like there's one TODO to resolve before this can be fully closed. |
Hey @BenHenning @adhiamboperes , Could you Please Clarify The changes That Need To Be Made? |
@TanishMoral11, per the TODO, it looks like the Bazel Linter needs to be added to the project. I think the specific details can be clarified later. Could you add this issue link to the CLaM meeting discussions thread: #5602? |
Is your feature request related to a problem? Please describe.
Currently, on GitHub checks, we are using Buildifier by downloading the binary and checking the file formatting.
Describe the solution you'd like
Try to implement with Bazel on GitHub checks as well as for pre-commit.
Additional context
Reference - https://github.com/bazelbuild/buildtools/blob/master/buildifier/README.md#setup-and-usage-via-bazel
Edit: The remaining bit is adding the buildifier to pre-push checks.
The text was updated successfully, but these errors were encountered: