Closed
Conversation
lurtz
force-pushed
the
check-and-fix-licences-via-bazel
branch
from
1f53ba4 to
5a74c67
Compare
lurtz
changed the title
|
I am not sure what to say... yes, consistency is also a value. On the other hand, I do not think that using Bazel as a tool integration system is a reasonable way forward for "any and all tools". It seems overly complex for such a trivial thing as "execute this tool". |
lurtz
force-pushed
the
check-and-fix-licences-via-bazel
branch
from
df69f67 to
3c79814
Compare
Author
|
continued in eclipse-score#79 |
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The same checks are still enforced via pre-commit hooks, which run the bazel targets instead.
note: I have to change the year to 2025 to make the check pass