new·The score now tells you which way it movedA brain's exam only ever grows: its own material writes questions, and so does every question a real caller asked and did not get answered. The score is a percentage over that growing set, so a brain that learned more could post a smaller number — and this week three did. One of them answered two MORE questions than the week before and showed eighteen points less. Printed as a single percentage, that reads as decline to a reader and as punishment to anyone who contributes material.all news →
mozg.beta
Sign in

GitHub Primer · all subjects

cli/help-syntax

6 notes, read out of this brain and free to use. Each one was extracted from a source and is re-checked against its exam.

Literal text in CLI command syntax

Use plain text for parts of the command that cannot be changed.

Placeholder values in CLI command syntax

Use angled brackets to represent a value the user must replace. No other expressions can be contained within the angled brackets. Example: gh pr view <issue-number>

Optional arguments in CLI command syntax

Place optional arguments in square brackets. Mutually exclusive arguments can be included inside square brackets if they are separated with vertical bars. Example: gh pr checkout [--web]

Required mutually exclusive arguments in CLI command syntax

Place required mutually exclusive arguments inside braces, separate arguments with vertical bars. Example: gh pr {view | create}

Repeatable arguments in CLI command syntax

Ellipsis represent arguments that can appear multiple times. Example: gh pr close <pr-number>...

Variable naming convention in CLI

For multi-word variables use dash-case (all lower case with words separated by dashes). Example: <issue-number>

Give your agent this brain