Pro Git 2nd Edition 2.1.413
each of which has a level of permissions for the group’s projects and the group itself. These range from “Guest” (issues and chat only) to “Owner” (full control of the group, its members, and its projects) repository on which others can base their work and which they can contribute to. This presents a vast range of workflow possibilities for your project and/or your team, so we’ll cover a few common paradigms last release or email is to use the git shortlog command. It summarizes all the commits in the range you give it; for example, the following gives you a summary of all the commits since your last release0 码力 | 731 页 | 21.49 MB | 1 年前3Pro Git 2nd Edition 2.1.413
users, each of which has a level of permissions for the group’s projects and the group itself. These range from “Guest” (issues and chat only) to “Owner” (full control of the group, its members, and its projects) repository on which others can base their work and which they can contribute to. This presents a vast range of workflow possibilities for your project and/or your team, so we’ll cover a few common paradigms last release or email is to use the git shortlog command. It summarizes all the commits in the range you give it; for example, the following gives you a summary of all the commits since your last release0 码力 | 501 页 | 17.96 MB | 1 年前3Pro Git 2nd Edition 2.1.413
each of which has a level of permissions for the group’s projects and the group itself. These range from “Guest” (issues and chat only) to “Owner” (full control of the group, its members, and its projects) repository on which others can base their work and which they can contribute to. This presents a vast range of workflow possibilities for your project and/or your team, so we’ll cover a few common paradigms last release or email is to use the git shortlog command. It summarizes all the commits in the range you give it; for example, the following gives you a summary of all the commits since your last release0 码力 | 691 页 | 13.35 MB | 1 年前3Gitea v1.21.1 中文文档
5000: 在diff视图中每行的最大字符数。 MAX_GIT_DIFF_FILES : 100: 在diff视图中显示的最大文件数。 COMMITS_RANGE_SIZE : 50: 设置默认的提交范围大小 BRANCHES_RANGE_SIZE : 20: 设置默认的分支范围大小 GC_ARGS : empty: 命令 git gc 的参数,例如 --aggressive --auto0 码力 | 303 页 | 3.88 MB | 1 年前3Pro Git 中文版 第2版 2.1.66
最常用的指明提交区间语法是双点。 这种语法可以让 Git 选出在一个分支中而不在另一个分支中的提交。 例 如,你有如下的提交历史 Example history for range selection. 图表 137. Example history for range selection. 你想要查看 experiment 分支中还有哪些提交尚未被合并入 master 分支。 你可以使用 master..experiment r.CommitObject(ref.Hash()) // 检索提交历史 history, err := commit.History() // 遍历并逐个打印提交 for _, c := range history { fmt.Println(c) } 高级功能 go-git 几乎没有值得注意的高级功能,其中之一是可插拔存储系统,类似于 Libgit2 后端。 默认实现是内存存 储,速度非常快。0 码力 | 501 页 | 19.30 MB | 1 年前3Pro Git 中文版 第2版 2.1.66
最常用的指明提交区间语法是双点。 这种语法可以让 Git 选出在一个分支中而 不在另一个分支中的提交。 例如,你有如下的提交历史 Example history for range selection. 图表 137. Example history for range selection. 你想要查看 experiment 分支中还有哪些提交尚未被合并入 master 分支。 你 可 以 使 用 master r.CommitObject(ref.Hash()) // 检索提交历史 history, err := commit.History() // 遍历并逐个打印提交 for _, c := range history { fmt.Println(c) } 高级功能 go-git 几乎没有值得注意的高级功能,其中之一是可插拔存储系统,类似于 Libgit2 后端。 默认实现是内存存储,速度非常快。0 码力 | 670 页 | 13.59 MB | 1 年前3
共 6 条
- 1