Welcome to mirror list, hosted at ThFree Co, Russian Federation.

gitlab.com/gitlab-org/gitaly.git - Unnamed repository; edit this file 'description' to name the repository.
summaryrefslogtreecommitdiff
path: root/doc
diff options
context:
space:
mode:
authorEvan Read <eread@gitlab.com>2023-06-13 01:57:22 +0300
committerEvan Read <eread@gitlab.com>2023-06-19 03:13:34 +0300
commit344f30ea3ca8357d5a1f5693e0e6bda3f17373a4 (patch)
tree27cc194b96eb1b524769b3b5f9dc57aae846b8d3 /doc
parent37a7580203ae39c3723644643a0943905976446f (diff)
Edit Praefect command usage strings
Diffstat (limited to 'doc')
-rw-r--r--doc/help_text_style_guide.md52
1 files changed, 48 insertions, 4 deletions
diff --git a/doc/help_text_style_guide.md b/doc/help_text_style_guide.md
index 4f4f764a8..f7e028961 100644
--- a/doc/help_text_style_guide.md
+++ b/doc/help_text_style_guide.md
@@ -36,17 +36,61 @@ keys for commands and subcommands:
| Field key | All lower case | Use period | Example key and value |
|:--------------|:---------------|:-----------|:--------------------------------------------------------------------------------------|
| `Name` | Yes | No | `Name: "example"` |
-| `Usage` | No | No | `Usage: "Short description of example command"` |
+| `Usage` | Yes | No | `Usage: "short description of example command"` |
| `Description` | No | Yes | `Description: "This is a long description of all the things example command can do."` |
+### Specific rules for `Usage`
+
+When providing values for the `Usage` field key:
+
+- Don't mention Gitaly or Praefect explicitly. We imply in the help text the tool we're referring to.
+
+ - Do:
+
+ ```plaintext
+ start the daemon
+ ```
+
+ - Don't:
+
+ ```plaintext
+ start the Gitaly daemon
+ ```
+
+- Always start with a verb and always write the string from the user's perspective, not the tool's perspective:
+
+ - Do:
+
+ ```plaintext
+ run the process
+ ```
+
+ - Don't:
+
+ ```plaintext
+ runs the process
+ ```
+
+ - Don't:
+
+ ```plaintext
+ the process runs
+ ```
+
### Specific rules for `Description`
-When providing values for the `Description` key:
+When providing values for the `Description` field key:
+
+- If referring to subcommands or flags, put the subcommand or flag in backticks. For example:
+
+ ```plaintext
+ `subcommand` can be run at any time with the `flag` flag.
+ ```
-- If referring to the subcommand itself, put the subcommand in backticks. For example:
+- Can mention Gitaly, Praefect, or Gitaly Cluster. For example:
```plaintext
- `subcommand` can be run at any time.
+ Runs all of the processes for the Gitaly Cluster.
```
## Related topics