-
Notifications
You must be signed in to change notification settings - Fork 58
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
[COMPLIANCE] Add Copyright and License Headers #202
Open
hashicorp-copywrite
wants to merge
1
commit into
master
Choose a base branch
from
compliance/add-headers
base: master
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Conversation
This file contains 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
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
February 13, 2023 16:30
cb0754a
to
9771b22
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
February 27, 2023 16:29
9771b22
to
81482b0
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
March 6, 2023 16:29
81482b0
to
54ba992
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
March 13, 2023 20:37
54ba992
to
a08342b
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
March 27, 2023 16:29
01e7bff
to
73dffb0
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
April 10, 2023 16:27
61e31c9
to
3a764c0
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
April 17, 2023 16:26
3a764c0
to
090daf5
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
April 24, 2023 16:27
090daf5
to
ae6bd08
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
May 8, 2023 16:26
c5488e6
to
9c4e852
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
May 22, 2023 16:26
e763548
to
a375ec8
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
May 29, 2023 16:26
a375ec8
to
9b88a19
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
June 12, 2023 16:29
8a84ccf
to
5a7f68b
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
June 19, 2023 16:26
5a7f68b
to
f79e38f
Compare
hashicorp-copywrite
bot
requested review from
a team,
shore and
emilymianeil
and removed request for
a team
June 19, 2023 16:26
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
July 3, 2023 16:26
9d8957a
to
ba27e17
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 24, 2023 16:26
ba27e17
to
25ff46d
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 31, 2023 16:30
25ff46d
to
98cf5a7
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
June 17, 2024 16:22
df03da2
to
c2dffe0
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
June 24, 2024 16:22
c2dffe0
to
a01ed3b
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
July 8, 2024 16:23
24d87fb
to
b6ce4ec
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
July 22, 2024 16:23
af0c46a
to
97a876c
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 29, 2024 16:23
97a876c
to
93f94ff
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
August 5, 2024 16:23
93f94ff
to
8f01c09
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
August 19, 2024 16:23
0b21f30
to
b242436
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
September 2, 2024 16:23
639a6db
to
6850c81
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
September 16, 2024 16:23
1e3e947
to
a61b522
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
September 23, 2024 16:23
a61b522
to
9eed5f8
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
October 7, 2024 16:23
8ac81af
to
11767e7
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
October 14, 2024 16:22
11767e7
to
d512cfb
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
October 21, 2024 16:23
d512cfb
to
0785d7d
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
November 4, 2024 16:23
6f6b644
to
a893f39
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
November 11, 2024 16:23
a893f39
to
a8bdbab
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
November 25, 2024 16:23
0687ba4
to
5b0b6b5
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
December 2, 2024 16:26
5b0b6b5
to
1215866
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
2 times, most recently
from
December 16, 2024 16:27
6f5c2e6
to
559d9e9
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
December 23, 2024 16:22
559d9e9
to
0eb33a9
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.
Hi there 👋
This PR was auto-generated as part of an internal review of public repositories that are not in compliance with HashiCorp's licensing standards.
Frequently Asked Questions
Why am I getting this PR?
This pull request was created because one or more source code files were found missing copyright and/or license headers.More info is available in the RFC
How do you determine which files should get copyright headers?
Attempts are made to skip scanning autogenerated files (e.g., `go.mod`) and prose. If you find file types you feel should be excluded from future scans, please reach out to:#proj-software-copyright
I have a file or folder which should be exempted, how do I do that?
You may exempt certain files or folders from being scanned by adding a `.copywrite.hcl` config in the root of your repo. You can use the [`copywrite init`](https://go.hashi.co/copywrite) command to interactively create a config for this project.An example schema can be found below. Add a doublestar**-capable pattern to the
header_ignore
list to skip it in future scans.I added a config. How do I trigger this PR to be rebased?
HashiCorp employees can use the [Copywrite SlackBot](https://hashicorp.slack.com/archives/D052WARFFS8) to trigger a rebase. You can DM the slackbot with "headers homebrew-tap" to trigger a PR rebasing.Why don't the headers include a copyright date?
Copyright headers are not required to include a year. In the interest of pragmatism, HashiCorp has decided to exclude the year from headers and instead list it in the LICENSE file at the root of the repository instead.Additional FAQs are available at https://go.hashi.co/header-faq
Please approve and merge this PR in a timely manner to keep this source code compliant with our OSS license agreement. If you have any questions or feedback, reach out to #proj-software-copyright.
Thank you!
Powered by copywrite, made with ❤️ by @hashicorp