Skip to content

Commit 23ffca4

Browse files
committed
Unify use of single quotes to mark shell arguments and variables
The first paragraph uses single quotes when referring to shell arguments and variables, but the rest of the docs use double quotes. This commit switches to using single quotes throughout the docs. I prefer to use single quotes inside string literals because Go uses double quotes to define a string literal.
1 parent 5314e7c commit 23ffca4

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

pkg/cmd/alias/set/set.go

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -43,9 +43,9 @@ func NewCmdSet(f *cmdutil.Factory, runF func(*SetOptions) error) *cobra.Command
4343
for commands with mixed quotes or multiple lines.
4444
4545
If '--shell' is specified, the alias will be run through a shell interpreter (sh). This allows you
46-
to compose commands with "|" or redirect with ">". Note that extra arguments following the alias
46+
to compose commands with '|' or redirect with '>'. Note that extra arguments following the alias
4747
will not be automatically passed to the expanded expression. To have a shell alias receive
48-
arguments, you must explicitly accept them using "$1", "$2", etc., or "$@" to accept all of them.
48+
arguments, you must explicitly accept them using '$1', '$2', etc., or '$@' to accept all of them.
4949
5050
Quotes must always be used when defining a command as in the examples unless you pass '-'
5151
as the expansion parameter and pipe your command to 'gh alias set'.

0 commit comments

Comments
 (0)