stable
Clone or download
Note this is already done by Git by default via the setting `receive.denyDeleteCurrent`. Nonetheless, even if it is protected by default it would not be the first time administrators play with settings they do not fully comprehend so having a complementary safety net is not a bad thing. To test: * you need to create the symlink to the new Gitolite VREF (checkout the specfile change to find out the source and target) * force a deployment of the Gitolite configuration (change a permissions in a repo somewhere, regenerate the conf of a project in site administration...) * disable the built-in Git protection in a repo (via `git config receive.denyDeleteCurrent ignore`) or globally Part of request #13356: Allow to change the default branch Change-Id: I724db34ee76d6cc835376bd36c0219fc50381544
Modified Files
Name | ||||
---|---|---|---|---|
A | plugins/git/bin/TULEAP_PROTECT_DEFAULT_BRANCH | +52 | −0 | Go to diff View file |
M | plugins/git/templates/gitolite/gitolite-with-hostname.conf.mustache | +1 | −0 | Go to diff View file |
M | plugins/git/templates/gitolite/gitolite.conf.mustache | +1 | −0 | Go to diff View file |
M | plugins/git/tests/unit/Git/Gitolite/_fixtures/default_gitolite.conf | +1 | −0 | Go to diff View file |
M | plugins/git/tests/unit/Git/Gitolite/_fixtures/mirrors_gitolite.conf | +1 | −0 | Go to diff View file |
M | tools/rpm/tuleap.rhel7.spec | +2 | −0 | Go to diff View file |