[JEWEL-978] Check Bazel build is up-to-date in GitHub CI #3247
Conversation
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
This change adds a script to validate that the IJP API dumps are up-to-date, and runs it in the GitHub Actions CI. It also rewrites the validate-api-dump-changes.main.kts script to use clikt as well.
rock3r
force-pushed
the
sebp/JEWEL-978_run-bazel-checker-on-gh-ci
branch
from
fe5eafe to
84b0361
Compare
This change adds a step to the GitHub CI to run the Bazel build generator script, and then check it has not made changes to any Bazel build files (ignoring the android submodule, which we do not care about). If it has, then the committer needs to run the script locally and commit & push these changes in the PR.
rock3r
force-pushed
the
sebp/JEWEL-978_run-bazel-checker-on-gh-ci
branch
from
84b0361 to
7ad17d1
Compare
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.
This change adds a step to the GitHub CI to run the Bazel build generator script, and then check it has not made changes to any Bazel build files (ignoring the android submodule, which we do not care about). If it has, then the committer needs to run the script locally and commit & push these changes in the PR.
Important
This PR requires #3245 (JEWEL-977) to be merged first