提交 02989309 编写于 作者: M Mislav Marohnić

Docs formatting issues

上级 9eb1a11d
...@@ -107,7 +107,9 @@ func (c *Command) Synopsis() string { ...@@ -107,7 +107,9 @@ func (c *Command) Synopsis() string {
} }
func (c *Command) HelpText() string { func (c *Command) HelpText() string {
return fmt.Sprintf("%s\n\n%s", c.Synopsis(), strings.Replace(c.Long, "'", "`", -1)) return fmt.Sprintf("%s\n\n%s",
strings.Replace(c.Synopsis(), "-^", "`-^`", 1),
strings.Replace(c.Long, "'", "`", -1))
} }
func (c *Command) Name() string { func (c *Command) Name() string {
......
...@@ -48,10 +48,10 @@ pull-request -i <ISSUE> ...@@ -48,10 +48,10 @@ pull-request -i <ISSUE>
-i, --issue=<ISSUE> -i, --issue=<ISSUE>
Convert an issue to a pull request. <ISSUE> may be an issue number or a URL. Convert an issue to a pull request. <ISSUE> may be an issue number or a URL.
You can only convert issues that you've opened or that which you have admin You can only convert issues authored by you or that which you have admin
rights over. In most workflows it isn't necessary to convert issues to pull rights over. In most workflows it is not necessary to convert issues to
requests; you can simply reference the original issue in the body of the new pull requests; you can simply reference the original issue in the body of
pull request. the new pull request.
-o, --browse -o, --browse
Open the new pull request in a web browser. Open the new pull request in a web browser.
...@@ -85,7 +85,7 @@ pull-request -i <ISSUE> ...@@ -85,7 +85,7 @@ pull-request -i <ISSUE>
-l, --labels=<LABELS> -l, --labels=<LABELS>
Add a comma-separated list of labels to this pull request. Labels will be Add a comma-separated list of labels to this pull request. Labels will be
created if they don't already exist. created if they do not already exist.
## Examples: ## Examples:
$ hub pull-request $ hub pull-request
...@@ -103,7 +103,7 @@ pull-request -i <ISSUE> ...@@ -103,7 +103,7 @@ pull-request -i <ISSUE>
## Configuration: ## Configuration:
HUB_RETRY_TIMEOUT=<SECONDS> * 'HUB_RETRY_TIMEOUT':
The maximum time to keep retrying after HTTP 422 on '--push' (default: 9). The maximum time to keep retrying after HTTP 422 on '--push' (default: 9).
## See also: ## See also:
......
...@@ -40,7 +40,7 @@ With '--exclude-prereleases', exclude non-stable releases from the listing. ...@@ -40,7 +40,7 @@ With '--exclude-prereleases', exclude non-stable releases from the listing.
* _create_: * _create_:
Create a GitHub release for the specified <TAG> name. If git tag <TAG> Create a GitHub release for the specified <TAG> name. If git tag <TAG>
doesn't exist, it will be created at <TARGET> (default: current branch). does not exist, it will be created at <TARGET> (default: current branch).
* _edit_: * _edit_:
Edit the GitHub release for the specified <TAG> name. Accepts the same Edit the GitHub release for the specified <TAG> name. Accepts the same
...@@ -93,7 +93,7 @@ With '--exclude-prereleases', exclude non-stable releases from the listing. ...@@ -93,7 +93,7 @@ With '--exclude-prereleases', exclude non-stable releases from the listing.
-t, --commitish=<TARGET> -t, --commitish=<TARGET>
A commit SHA or branch name to attach the release to, only used if <TAG> A commit SHA or branch name to attach the release to, only used if <TAG>
doesn't already exist (default: main branch). does not already exist (default: main branch).
-f, --format=<FORMAT> -f, --format=<FORMAT>
Pretty print releases using <FORMAT> (default: "%T%n"). See the "PRETTY Pretty print releases using <FORMAT> (default: "%T%n"). See the "PRETTY
......
...@@ -21,7 +21,7 @@ var cmdSync = &Command{ ...@@ -21,7 +21,7 @@ var cmdSync = &Command{
- If the local branch contains unpushed work, warn about it; - If the local branch contains unpushed work, warn about it;
- If the branch seems merged and its upstream branch was deleted, delete it. - If the branch seems merged and its upstream branch was deleted, delete it.
If a local branch doesn't have any upstream configuration, but has a If a local branch does not have any upstream configuration, but has a
same-named branch on the remote, treat that as its upstream branch. same-named branch on the remote, treat that as its upstream branch.
## See also: ## See also:
......
Markdown is supported
0% .
You are about to add 0 people to the discussion. Proceed with caution.
先完成此消息的编辑!
想要评论请 注册