-
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
Header Improvements (File description and scope) #706
Comments
We actually have a standard on the use of a proper license header that needs to be documented ... We need the boilerplate block to make the K8s lawyers happy, to be able to run the header checker that I have. Another code block afterward I think is awesome. See: https://github.com/kubernetes/kops/tree/master/hack/boilerplate |
Makes sense..
This works for me |
FYI -
We need to figure out the auto gen code because it does not have a header. We need this in our CI |
Would like to propose a format to start including descriptive headers in kops code.
Digging into kops is fun, but I am constantly referencing my notes as I explore the code base.
I think it would be helpful to store descriptions and code docs in the files themselves. Not a hard requirement, but it would be nice to have an agreed upon format and blessing to start doing this if an engineer so desires
Thoughts?
The text was updated successfully, but these errors were encountered: