Files
kubernetes/hack
Patrick Ohly cf2e6291d1 hack: move golangci-lint config files
Because the script now explicitly selects the configuration file, the files no
longer have to be in the root directory. Having them in hack without the
leading dot is better because they then have the same owners as the script and
are more visible.

The downside is that manual invocations of golangci-lint without the parameter
no longer work.
2023-02-28 17:22:31 +01:00
..
2021-02-28 15:17:29 -08:00
2022-02-14 10:55:35 -07:00
2023-02-01 16:34:23 -05:00
2022-06-26 09:21:05 +05:30
2019-01-22 08:39:55 +08:00
2019-01-22 08:39:55 +08:00
2022-07-08 10:46:11 +08:00
2022-10-10 13:43:03 -04:00
2020-01-16 10:12:18 +08:00
2020-01-28 09:27:40 +09:00
2023-01-22 15:16:23 -08:00
2022-10-19 17:27:25 +00:00
2023-01-12 11:20:41 +08:00
2021-03-07 12:51:33 -08:00
2023-01-12 11:20:41 +08:00
2020-09-03 23:29:07 +00:00

Kubernetes hack GuideLines

This document describes how you can use the scripts from hack directory and gives a brief introduction and explanation of these scripts.

Overview

The hack directory contains many scripts that ensure continuous development of kubernetes, enhance the robustness of the code, improve development efficiency, etc. The explanations and descriptions of these scripts are helpful for contributors. For details, refer to the following guidelines.

Key scripts

  • verify-all.sh: This script is a vestigial redirection, Please do not add "real" logic. It is equivalent to make verify.
  • update-all.sh: This script is a vestigial redirection, Please do not add "real" logic. The true target of this makerule is hack/make-rules/update.sh.It is equivalent to make update.

Attention

Note that all scripts must be run from the Kubernetes root directory. We should run hack/verify-all.sh before submitting a PR and if anything fails run hack/update-all.sh.