Files
kubernetes/hack
Stephen Kitt f040d9012c verify-no-vendor-cycles: set up Go environment
This script relies on Go but doesn't set up the private Go environment
(which ensures that the go command meets k/k's requirements). This
fixes that.

As a drive-by improvement, drop two unnecessary backslashes from
regexes (before / which doesn't need to be escaped).

Signed-off-by: Stephen Kitt <skitt@redhat.com>
2023-11-10 10:58:53 +01:00
..
2023-05-30 00:58:32 +03:00
2021-02-28 15:17:29 -08:00
2023-11-02 10:30:41 +01:00
2023-10-26 15:32:43 +02: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
2023-05-31 12:53:11 +03:00
2023-05-11 16:43:38 +00:00
2020-01-16 10:12:18 +08:00
2023-01-22 15:16:23 -08:00
2023-04-21 16:15:21 -07: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

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.