that will be made should this branch get merged by the project owner. Figure 91. Pull Request creation page When you hit the 'Create pull request' button on this screen, the owner of the project you S_ISGITLINK(m) (((m) & S_IFMT) == S_IFGITLINK) v1.8.0:environment.c 54:#define OBJECT_CREATION_MODE OBJECT_CREATION_USES_HARDLINKS v1.8.0:strbuf.c 326:#define STRBUF_MAXLINK (2*PATH_MAX) v1.8.0:symlinks behaves. Let’s take a look at the file in the root: [repo-creation] charset = utf8 [git-to-perforce] change-owner = author enable-git-branch-creation = yes enable-swarm-reviews = yes enable-git-merge-commits

will be made should this branch get merged by the project owner. 175 Figure 91. Pull Request creation page When you hit the 'Create pull request' button on this screen, the owner of the project you S_ISGITLINK(m) (((m) & S_IFMT) == S_IFGITLINK) v1.8.0:environment.c 54:#define OBJECT_CREATION_MODE OBJECT_CREATION_USES_HARDLINKS v1.8.0:strbuf.c 326:#define STRBUF_MAXLINK (2*PATH_MAX) v1.8.0:symlinks Let’s take a look at the file in the root: 387 [repo-creation] charset = utf8 [git-to-perforce] change-owner = author enable-git-branch-creation = yes enable-swarm-reviews = yes enable-git-merge-commits

that will be made should this branch get merged by the project owner. Figure 91. Pull Request creation page When you hit the 'Create pull request' button on this screen, the owner of the project you S_ISGITLINK(m) (((m) & S_IFMT) == S_IFGITLINK) v1.8.0:environment.c 54:#define OBJECT_CREATION_MODE OBJECT_CREATION_USES_HARDLINKS v1.8.0:strbuf.c 326:#define STRBUF_MAXLINK (2*PATH_MAX) v1.8.0:symlinks behaves. Let’s take a look at the file in the root: [repo-creation] charset = utf8 [git-to-perforce] change-owner = author enable-git-branch-creation = yes enable-swarm-reviews = yes enable-git-merge-commits

S_ISGITLINK(m) (((m) & S_IFMT) == S_IFGITLINK) v1.8.0:environment.c 54:#define OBJECT_CREATION_MODE OBJECT_CREATION_USES_HARDLINKS v1.8.0:strbuf.c 326:#define STRBUF_MAXLINK (2*PATH_MAX) v1.8.0:symlinks 文件，每个仓库中也会有一份——这些配置文件决定了 Git Fusion 的行为。 让我们看一下根目录下的文件： 386 [repo-creation] charset = utf8 [git-to-perforce] change-owner = author enable-git-branch-creation = yes enable-swarm-reviews = yes enable-git-merge-commits

S_ISGITLINK(m) (((m) & S_IFMT) == S_IFGITLINK) v1.8.0:environment.c 54:#define OBJECT_CREATION_MODE OBJECT_CREATION_USES_HARDLINKS v1.8.0:strbuf.c 326:#define STRBUF_MAXLINK (2*PATH_MAX) v1.8.0:symlinks 每个仓库中也会有一份——这些配置文件决定了 Git Fusion 的行为。 让我们 看一下根目录下的文件： [repo-creation] charset = utf8 [git-to-perforce] change-owner = author enable-git-branch-creation = yes enable-swarm-reviews = yes enable-git-merge-commits

创建新仓库时默认为私有。 [last, private, public] DEFAULT_PUSH_CREATE_PRIVATE : true: 使用推送创建新仓库时默认为私有。 MAX_CREATION_LIMIT : -1: 每个用户的全局仓库创建上限, -1 代表无限制. PREFERRED_LICENSES : Apache License 2.0,MIT License: 要放置在列表顶部的指定许可证。 DEFAULT_EMAIL_NOTIFICATIONS : enabled：用户电子邮件通知的默认配置（用户可配置）。选项：enabled、 onmention、disabled DISABLE_REGULAR_ORG_CREATION : false：禁止普通（非管理员）用户创建组织。 INSTALL_LOCK : false：控制是否能够访问安装向导页面，设置为 true 则禁止访问安装向导页面。 SECRET_KEY