Repository navigation
Add the Datadog license header to Bazel build files - #11
Merged
Merged
Conversation
Datadog's OSS release policy asks for the repository license header in every file. Source, scripts and Python already carry it; the BUILD.bazel and MODULE.bazel files did not.
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
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.
What does this PR do?
Adds the repository license header to the 11
BUILD.bazelandMODULE.bazelfiles that lacked it. Rust, shell and Python sources already carry it.Checks: no first-party source or build file is missing the header;
bazel test //...passes;MODULE.bazel.lockis unchanged.Part of preparing conduit for transfer to the DataDog organization as an open source repository.
Checklist