Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
github
hub
提交
02989309
H
hub
项目概览
github
/
hub
接近 1 年 前同步成功
通知
3
Star
22523
Fork
2406
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
H
hub
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
02989309
编写于
12月 28, 2018
作者:
M
Mislav Marohnić
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Docs formatting issues
上级
9eb1a11d
变更
4
隐藏空白更改
内联
并排
Showing
4 changed file
with
12 addition
and
10 deletion
+12
-10
commands/commands.go
commands/commands.go
+3
-1
commands/pull_request.go
commands/pull_request.go
+6
-6
commands/release.go
commands/release.go
+2
-2
commands/sync.go
commands/sync.go
+1
-1
未找到文件。
commands/commands.go
浏览文件 @
02989309
...
@@ -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
{
...
...
commands/pull_request.go
浏览文件 @
02989309
...
@@ -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 is
n'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 do
n'
t already exist.
created if they do
no
t 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:
...
...
commands/release.go
浏览文件 @
02989309
...
@@ -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>
does
n'
t exist, it will be created at <TARGET> (default: current branch).
does
no
t 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>
does
n'
t already exist (default: main branch).
does
no
t 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
...
...
commands/sync.go
浏览文件 @
02989309
...
@@ -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 does
n'
t have any upstream configuration, but has a
If a local branch does
no
t 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.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录