output of the git status command commented out and one empty line on top. You can remove these comments and type your commit message, or you can leave them there to help you remember what you’re committing committing. When you exit the editor, Git creates your commit with that commit message (with the comments and diff stripped out). Alternatively, you can type your commit message inline with the commit notifications turned on, Tony would get an email like this: Figure 93. Comments sent as email notifications Anyone can also leave general comments on the Pull Request. In Pull Request discussion page we can see

output of the git status command commented out and one empty line on top. You can remove these comments and type your commit 36 message, or you can leave them there to help you remember what you’re committing. When you exit the editor, Git creates your commit with that commit message (with the comments and diff stripped out). Alternatively, you can type your commit message inline with the commit notifications turned on, Tony would get an email like this: Figure 93. Comments sent as email notifications Anyone can also leave general comments on the Pull Request. In Pull Request discussion page we can see

output of the git status command commented out and one empty line on top. You can remove these comments and type your commit message, or you can leave them there to help you remember what you’re committing committing. When you exit the editor, Git creates your commit with that commit message (with the comments and diff stripped out). Alternatively, you can type your commit message inline with the commit notifications turned on, Tony would get an email like this: Figure 93. Comments sent as email notifications Anyone can also leave general comments on the Pull Request. In Pull Request discussion page we can see

：要迁移的项目，一个或多个项目应以逗号分隔。允许的项目有 wiki, issues, labels, releases, release_assets, milestones, pull_requests, comments。如果为 空，则表示所有项目。 restore-repo 从磁盘目录中还原存储库数据： 选项： --repo_dir dir ， -r dir ：还原数据的存储库目录路径。 ：要还原的项目，一个或多个项目应以逗号分隔。允许的项目有 wiki, issues, labels, releases, release_assets, milestones, pull_requests, comments。如果为 空，则表示所有项目。 生成一个供 Runner 使用的新令牌，用于向服务器注册。 选项： --scope {owner}[/{repo}] ， -s {owner}[/{repo}] MAX_FILE_SIZE : 524288 (512kb): 以字节为单位允许将CSV文件呈现为表格的最大文件大小（将其设置为0 表示没有限制）。 ENABLE_HARD_LINE_BREAK_IN_COMMENTS : true: 在评论中将软换行符呈现为硬换行符， 这意味着段落之间的单 个换行符将导致换行， 并且不需要在段落后添加尾随空格来强制换行。 ENABLE_HARD_LINE_BREAK_IN_DOCUMENTS

想要对一个特定问题 Issue #6 留下一条评论。 必须使用 刚刚生成的令牌作为 Authorization 头信息，发送一个到 repos///issues//comments 的 HTTP POST 请求。 213 $ curl -H "Content-Type: application/json" \ -H "Authorization: token --data '{"body":"A new comment, :+1:"}' \ https://api.github.com/repos/schacon/blink/issues/6/comments { "id": 58322100, "html_url": "https://github.com/schacon/blink/issues/6#issuecomment- 58322100" Read-only. # Type: Either 'public' or 'restricted'. Default is 'public'. # Description: Comments about the changelist. Required. # Jobs: What opened jobs are to be closed by this changelist

Issue #6 留下一条评论。 必须使用刚刚生成的令牌作为 Authorization 头信 息 ， 发 送 一 个 到 repos///issues//comments 的 HTTP POST 请求。 $ curl -H "Content-Type: application/json" \ -H "Authorization: token --data '{"body":"A new comment, :+1:"}' \ https://api.github.com/repos/schacon/blink/issues/6/comments { "id": 58322100, "html_url": "https://github.com/schacon/blink/issues/6#issuecomment-58322100" Read-only. # Type: Either 'public' or 'restricted'. Default is 'public'. # Description: Comments about the changelist. Required. # Jobs: What opened jobs are to be closed by this changelist