| commit | 6c59f2a53bca782ac606ca78526235da74f1fe33 | |
| author | Sitaram Chamarty <sitaram@atc.tcs.com> | |
| Sat, 6 Feb 2016 03:24:37 +0000 (6 08:54 +0530) | ||
| committer | Sitaram Chamarty <sitaram@atc.tcs.com> | |
| Sat, 6 Feb 2016 04:52:24 +0000 (6 10:22 +0530) | ||
| tree | 4e8a47eea0a84c79e0e9d5ecd84b03f3d1756c44 | treesnapshot (tar.gz zip) |
| parent | 8de9b8d37eb7a0ad9915f49da9c699d8216a1fb0 | commitdiff |
allow creator check to be bypassed during mirroring...
The original, intended, purpose of wild repos is that they belong to the user,
and if the user is gone, so should his wild repos.
However, it seems people are using the wild repos thing as a convenience to
avoid creating actual repo stanzas in the conf file. For them, the actual
creator of a repo is more like the gitolite "admin" - his *authority* is being
to used to create something, but the thing that is created is not tied to his
*identity*.
Oh well... so be it!
To use, just add
option bypass-creator-check = 1
to the rules for the repo.
The original, intended, purpose of wild repos is that they belong to the user,
and if the user is gone, so should his wild repos.
However, it seems people are using the wild repos thing as a convenience to
avoid creating actual repo stanzas in the conf file. For them, the actual
creator of a repo is more like the gitolite "admin" - his *authority* is being
to used to create something, but the thing that is created is not tied to his
*identity*.
Oh well... so be it!
To use, just add
option bypass-creator-check = 1
to the rules for the repo.
| src/commands/perms | diffblobblamehistory | |
| src/lib/Gitolite/Triggers/Mirroring.pm | diffblobblamehistory |