-
Notifications
You must be signed in to change notification settings - Fork 15
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 #42
Open
hashicorp-copywrite
wants to merge
1
commit into
main
Choose a base branch
from
compliance/add-headers
base: main
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
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
March 6, 2023 16:53
d7ce586
to
12cb64f
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
March 13, 2023 21:00
12cb64f
to
456ae88
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
March 20, 2023 16:53
456ae88
to
0b4993d
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
April 3, 2023 16:50
0b4993d
to
84d9901
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
April 10, 2023 16:49
84d9901
to
6dc5db5
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
April 24, 2023 16:48
6dc5db5
to
ccd33b8
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
May 8, 2023 16:47
ccd33b8
to
193010b
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
May 15, 2023 16:48
193010b
to
ba2a0c0
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
June 12, 2023 16:51
ba2a0c0
to
90e9252
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 10, 2023 16:50
90e9252
to
98a47d0
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 24, 2023 16:47
98a47d0
to
f44da4b
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 31, 2023 16:54
f44da4b
to
10aa9a7
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
September 4, 2023 16:50
10aa9a7
to
8824c11
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
September 18, 2023 16:49
8824c11
to
71c0067
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
May 6, 2024 16:43
772bf3a
to
b43ac32
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
May 13, 2024 16:42
b43ac32
to
3c0e516
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
June 3, 2024 16:43
3c0e516
to
63afac2
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 8, 2024 16:42
63afac2
to
337471f
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 15, 2024 16:42
337471f
to
ca2d7df
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 29, 2024 16:42
ca2d7df
to
6e4c828
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
August 19, 2024 16:43
6e4c828
to
4f393b9
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
August 26, 2024 16:46
4f393b9
to
a8c7884
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
September 23, 2024 16:42
a8c7884
to
0500371
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
October 7, 2024 16:42
0500371
to
5c554eb
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
October 28, 2024 16:43
5c554eb
to
8377cdf
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
November 4, 2024 16:43
8377cdf
to
6f34dc0
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
November 11, 2024 16:42
6f34dc0
to
44bbf5c
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
November 18, 2024 16:44
44bbf5c
to
b88a63f
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 terraform-docs-agents" 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