-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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 #22657
Closed
Closed
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
July 24, 2023 16:10
63c923d
to
cab16d0
Compare
github-actions
bot
added
dependencies
service/storage
service/key-vault
Key Vault
service/app-service
service/automation
service/data-factory
service/batch
service/kusto
service/maintenance
service/authorization
service/load-test
service/mobile-network
service/graph
size/XL
waiting-response
labels
Jul 24, 2023
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
July 31, 2023 16:11
cab16d0
to
73079af
Compare
github-actions
bot
added
service/event-hubs
EventHubs
service/network
service/network-function
waiting-response
and removed
waiting-response
labels
Jul 31, 2023
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
August 7, 2023 16:09
73079af
to
14a116a
Compare
github-actions
bot
added
service/event-grid
EventGrid
tooling
waiting-response
and removed
waiting-response
labels
Aug 7, 2023
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
August 14, 2023 16:09
14a116a
to
ef74e00
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
October 23, 2023 16:09
f5b33e9
to
9dd0b3d
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
October 30, 2023 16:10
9dd0b3d
to
113c668
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
November 6, 2023 16:14
113c668
to
1e6e886
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
November 13, 2023 16:09
1e6e886
to
22f725f
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
November 20, 2023 16:10
22f725f
to
a5c3297
Compare
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
November 27, 2023 16:10
a5c3297
to
c484e53
Compare
github-actions
bot
added
service/dns
waiting-response
and removed
waiting-response
labels
Nov 27, 2023
hashicorp-copywrite
bot
force-pushed
the
compliance/add-headers
branch
from
December 4, 2023 16:10
c484e53
to
5db2a1e
Compare
github-actions
bot
added
service/azure-stack-hci
service/elasticsan
waiting-response
and removed
waiting-response
labels
Dec 4, 2023
I'm going to lock this pull request because it has been closed for 30 days ⏳. This helps our maintainers find and focus on the active contributions. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Labels
automated
dependencies
legal
service/api-management
service/app-configuration
service/app-service
service/arc-resource-bridge
service/authorization
service/automation
service/azure-stack-hci
service/azuremanagedlustrefilesystem
service/batch
service/data-factory
service/dev-center
service/dns
service/elasticsan
service/event-grid
EventGrid
service/event-hubs
EventHubs
service/graph
service/key-vault
Key Vault
service/kusto
service/load-test
service/maintenance
service/mobile-network
service/mssql
Microsoft SQL Server
service/network
service/network-function
service/paloalto
service/security-center
service/service-connector
service/service-networking
service/spring
service/storage
size/XL
state-migration
tooling
waiting-response
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-provider-azurerm" 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