pub const ISSUE_CREATE: &str = "\
Create an issue.
```
ytcli issue create -q PROJ -s \"Attachments are lost on move\"
ytcli issue create -q PROJ -s \"title\" -d \"body\" --assignee login --tags QA,P6
ytcli issue create -q PROJ -s \"title\" --description-file ./body.md
ytcli issue create -q PROJ -s \"title\" -d - # the body from stdin
ytcli issue create -q PROJ -s \"title\" --dry-run
```
A description is the field most likely to hold quotes, newlines and markdown, so
it can come from a file or from stdin rather than from an argument. Both at once
is an error, not a precedence rule: guessing which was meant is how the wrong
text gets written.
Descriptions and comments are drawn as Yandex Flavored Markdown. The older wiki
spellings still render alongside it, but a `#` starting a line is a heading in
both, never a list marker: number a list with `1.` and head a section with `##`.
The wrong one renders without an error, so nothing but the reader will say so.
Prints the profile and organisation it is about to write to before it writes.
`--dry-run` shows the request body and sends nothing.
Failed writes are not retried: a retried write can be a duplicated one.";