chore: make all file headers consistent#4075
Conversation
|
Hi @alexandear. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
/ok-to-test |
|
/lgtm |
|
LGTM label has been added. DetailsGit tree hash: 8933e7facf8c998350ad3374258590a1f0e36e80 |
caa0c38 to
7df11a8
Compare
7df11a8 to
6d59dc5
Compare
|
/lgtm |
|
LGTM label has been added. DetailsGit tree hash: 1138571cdaf87a97628b6739a8f43f593b9d98a6 |
|
/retest Due to #4113. |
6d59dc5 to
f350e67
Compare
f350e67 to
a906ccd
Compare
a906ccd to
6621ce6
Compare
6621ce6 to
bc363f7
Compare
|
Thanks for the PR! Could we make goheader part of |
It's already part of Or maybe you mean adding a new |
|
/lgtm
Great! Thanks for clarifying |
|
LGTM label has been added. DetailsGit tree hash: da65afcd73f5b114065e5c9486a8b689e27d5c3c |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alexandear, tenzen-y The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
* chore: make all file headers consistent * Remove year from copyright; use template-path
* chore: make all file headers consistent * Remove year from copyright; use template-path
What type of PR is this?
/kind cleanup
What this PR does / why we need it:
Fixes copyright headers for Go files and make it consistent. Integrates
goheaderlinter to automatically check the file header.Special notes for your reviewer:
Changes:
About
goheaderlinter: https://golangci-lint.run/usage/linters/#goheaderDoes this PR introduce a user-facing change?