-
Notifications
You must be signed in to change notification settings - Fork 542
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
Copyright headers #916
Comments
I'm guessing the answer is probably "yes". I emailed our licensing people on the off chance the answer is "no" |
I heard back: the answer is yes, they should all have the copyright notice |
* Add missing copyright headers Done by running: `addlicense -v -c "The Bazel Authors. All rights reserved." .` With a few changes reverted because they're for generated files or test goldens. Fixes #916
After talking with some lawyers, the couple generated files I skipped initially also need to have copyright headers added (just to the checked in file in our repo, the code-generator won't emit a copyright header). Gonna re-open this to address that. |
Closing. We fixed |
This is a housekeeping issue for the repo. I am noticing that we do not have copyright headers on the code files. See here: https://github.com/bazelbuild/bazel/blob/master/src/create_embedded_tools.py#L3 for an example of the header I a referring to. The go_fules repo uses the "addlicense" tool to update the headers in the code.
Is this something we should have in this repo as well?
The text was updated successfully, but these errors were encountered: