github
/
k3s
mirror of https://github.com/k3s-io/k3s
1
0
Fork 0
Code Issues Projects Releases Wiki Activity
k3s/hack/after-build
History
Chao Xu 530a9a0238 cover expapi when genereate types_swagger_doc_generated.go 2015-09-02 10:01:40 -07:00
..
README.md Split hack/{verify,update}-* files so we don't always go build 2015-08-11 14:20:46 -04:00
update-generated-conversions.sh Do not use goimports in hack/update-generated-conversions.sh 2015-08-13 19:37:01 -04:00
update-generated-deep-copies.sh Convert generated-deep-copies to use golang.org/x/tools/imports 2015-08-13 19:36:57 -04:00
update-generated-docs.sh Split hack/{verify,update}-* files so we don't always go build 2015-08-11 14:20:46 -04:00
update-swagger-spec.sh Use a valid address for swagger 2015-08-18 21:50:27 -07:00
verify-description.sh cover expapi when genereate types_swagger_doc_generated.go 2015-09-02 10:01:40 -07:00
verify-generated-conversions.sh Do not build genconversion and gendeepcopy twice 2015-08-12 10:05:48 -04:00
verify-generated-deep-copies.sh Do not build genconversion and gendeepcopy twice 2015-08-12 10:05:48 -04:00
verify-generated-docs.sh Split hack/{verify,update}-* files so we don't always go build 2015-08-11 14:20:46 -04:00
verify-generated-swagger-docs.sh hack and hooks scripts for generating swagger docs 2015-08-22 02:27:41 +02:00
verify-linkcheck.sh Split hack/{verify,update}-* files so we don't always go build 2015-08-11 14:20:46 -04:00
verify-swagger-spec.sh Split hack/{verify,update}-* files so we don't always go build 2015-08-11 14:20:46 -04:00

README.md

These should be called only by a script (or a user) who knows that the binaries are built and correct. Normal users should just have the versions in ../ which should just always do a build.

Analytics