summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authork8s-merge-robot <k8s.production.user@gmail.com>2016-07-07 00:12:22 -0700
committerGitHub <noreply@github.com>2016-07-07 00:12:22 -0700
commit0bafb2a75bafe53632284c8b4ff62401a32a4822 (patch)
tree6cf53d63df0ef5e8df9e95c27c8e97d8ce7ae5ad
parent17596a7ef5cbc326813badeed329327842ef5eda (diff)
parent91f816494452b3a9a4e39117bdadb7b64279c8e2 (diff)
Merge pull request #26977 from joe2far/fix-help-strings
Automatic merge from submit-queue Make kubectl help strings consistent
-rw-r--r--kubectl-conventions.md10
1 files changed, 10 insertions, 0 deletions
diff --git a/kubectl-conventions.md b/kubectl-conventions.md
index 0beb95a7..40cb7e59 100644
--- a/kubectl-conventions.md
+++ b/kubectl-conventions.md
@@ -125,6 +125,9 @@ flags and separate help that is tailored for the particular usage.
* Flag names and single-character aliases should have the same meaning across
all commands
+* Flag descriptions should start with an uppercase letter and not have a
+period at the end of a sentence
+
* Command-line flags corresponding to API fields should accept API enums
exactly (e.g., `--restart=Always`)
@@ -233,9 +236,16 @@ resources in other commands
an exhaustive specification
* Short should contain a one-line explanation of what the command does
+ * Short descriptions should start with an uppercase case letter and not
+ have a period at the end of a sentence
+ * Short descriptions should (if possible) start with a first person
+ (singular present tense) verb
* Long may contain multiple lines, including additional information about
input, output, commonly used flags, etc.
+ * Long descriptions should use proper grammar, start with an uppercase
+ letter and have a period at the end of a sentence
+
* Example should contain examples
* Start commands with `$`