You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using code-generator to generate files, the boilerplate is used and it contains YEAR field in copyright, so when we generate new files in current year, the year will be rendered, but the previous files will also be affected, which is unacceptable, and from kubernetes's practice, see kubernetes/gengo#24, there are no YEAR field in license header, so I suggest remove the YEAR field too, cause it has nothing to do with the license.
Describe the solution you'd like
Remove copyright year from generated go files, currently only API repo https://github.com/volcano-sh/apis has this problem, we can first start with the API repo.
Additional context
This pr volcano-sh/apis#134 is doing this when updating code generation scripts.
The text was updated successfully, but these errors were encountered:
Instructions 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/test-infra repository.
What is the problem you're trying to solve
When using code-generator to generate files, the boilerplate is used and it contains YEAR field in copyright, so when we generate new files in current year, the year will be rendered, but the previous files will also be affected, which is unacceptable, and from kubernetes's practice, see kubernetes/gengo#24, there are no YEAR field in license header, so I suggest remove the YEAR field too, cause it has nothing to do with the license.
Describe the solution you'd like
Remove copyright year from generated go files, currently only API repo https://github.com/volcano-sh/apis has this problem, we can first start with the API repo.
Additional context
This pr volcano-sh/apis#134 is doing this when updating code generation scripts.
The text was updated successfully, but these errors were encountered: