Skip to content

Comments

[COMPLIANCE] Add Copyright and License Headers#4440

Open
hashicorp-copywrite[bot] wants to merge 1 commit intomainfrom
compliance/add-headers
Open

[COMPLIANCE] Add Copyright and License Headers#4440
hashicorp-copywrite[bot] wants to merge 1 commit intomainfrom
compliance/add-headers

Conversation

@hashicorp-copywrite
Copy link
Contributor

@hashicorp-copywrite hashicorp-copywrite bot commented Dec 2, 2024

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.

# (OPTIONAL) Overrides the copywrite config schema version
# Default: 1
schema_version = 1

project {
  # (OPTIONAL) SPDX-compatible license identifier
  # Leave blank if you don't wish to license the project
  # Default: "MPL-2.0"
  # license = ""

  # (OPTIONAL) Represents the year that the project initially began
  # Default: <the year the repo was first created>
  # copyright_year = 0

  # (OPTIONAL) A list of globs that should not have copyright or license headers .
  # Supports doublestar glob patterns for more flexibility in defining which
  # files or folders should be ignored
  # Default: []
  header_ignore = [
    # "vendor/**",
    # "**autogen**",
  ]
}

More information about configuration options is available in [the documentation](https://github.com/hashicorp/copywrite#config-structure).
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 consul-k8s" 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

@hashicorp-copywrite hashicorp-copywrite bot requested a review from a team as a code owner December 2, 2024 16:16
@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch 2 times, most recently from d5eaf66 to cd46f9a Compare March 24, 2025 16:13
@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch from cd46f9a to 733744a Compare April 21, 2025 16:12
@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch from 733744a to 6d1fbb0 Compare May 12, 2025 16:12
@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch 2 times, most recently from 61f6580 to 55177a5 Compare May 26, 2025 16:11
@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch 2 times, most recently from 4176d5b to 43ef683 Compare June 9, 2025 16:12
@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch from 43ef683 to b412c45 Compare June 16, 2025 16:12
srahul3
srahul3 previously approved these changes Jun 24, 2025
Copy link
Contributor

@srahul3 srahul3 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ LGTM

@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch 2 times, most recently from 9f615f0 to 3acc9a1 Compare July 7, 2025 16:11
@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch from 3acc9a1 to 1fe51f9 Compare July 14, 2025 16:11
@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch from 1fe51f9 to 103d6b8 Compare July 28, 2025 16:12
@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch 2 times, most recently from 85e5dbf to 5ceac52 Compare August 11, 2025 16:12
@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch 2 times, most recently from d40423d to e2fd988 Compare September 1, 2025 16:11
@hashicorp-copywrite hashicorp-copywrite bot force-pushed the compliance/add-headers branch 2 times, most recently from c3d6d1c to 2cdca44 Compare September 15, 2025 16:12
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant