Commits on Apr 12, 2017
  1. (untested) namespace support...

    -   see for details
    -   last time this was tested, "taxpayer funded" and "cyber criminals" were
        mutually exclusive phrases ;-)
    committed Nov 16, 2012
Commits on Apr 4, 2017
Commits on Mar 27, 2017
Commits on Jan 16, 2017
Commits on Jan 14, 2017
  1. allow @group names in config values to be expanded...

    The string "@group" is replaced with a space separated list of member
    names if it is a valid group.  Otherwise it is left alone.
    committed Jan 14, 2017
Commits on Nov 25, 2016
  1. fix shebang in repo-specific-hooks

    (thanks to Dieter on the mailing list for catching this!)
    committed Nov 25, 2016
Commits on Sep 30, 2016
  1. fix up command help for 'list-users' and 'list-members'

    ...was incomplete/ambiguous
    committed Sep 30, 2016
Commits on Sep 9, 2016
  1. (minor) patch typo in default .rc

    kwadronaut committed with Sep 8, 2016
Commits on Sep 8, 2016
  1. v3.6.6

    committed Sep 8, 2016
  2. fix 'access' command behaviour for 'C' and 'D' perms

    Thanks to Alexander Groß for catching this.  Basically, the access command was
    ignoring the presence or absence
    committed Sep 8, 2016
Commits on Sep 5, 2016
  1. minor README change

    See mailing list thread, subject line "Readme-extensions"
    committed Sep 5, 2016
  2. prep for perl 5.26 removing "." from @INC

    Someone on irc found that debian -- per [1] -- has already implemented it, so
    gitolite fails.
    This fix is useful even on older perls; I should have done it long ago.  (It
    prevents perl searching all over @INC for the file when we *know* it's right
    here under $PWD).
    committed Sep 5, 2016
Commits on Aug 31, 2016
  1. ssh-authkeys-split: do not zap keys without trailing newlines

    The normal ssh-authkeys script handles key files without trailing newlines
    OK. However ssh-authkeys-split does not, because it tries to treat a
    zero-newline file as a multi-line file, and the shell `read` builtin will
    not read a line that ends with eof rather than a newline. So it ends up
    discarding zero-newline keys.
    fanf2 committed with Aug 31, 2016
Commits on Jun 16, 2016
  1. suppress warnings when trying to clean repo hook

    suppress warning when setting the repo-specific hooks to an empty
    string, e.g. removing an existing hook.
    Specifically, we default repositories to use a repo-specific hook:
    repo @all
        option = jenkins
    this causes gitolite to output a warning that it is ignoring the attempt
    to set a post-update hook on the admin repository.    I'd like to be
    able to do:
    repo gitolite-admin
        option = ""
    but the warning is printed before it realizes that the argument is empty.
    This patch just changes the order of the checks so that the warning is
    only printed if the hooks are actually defined.
    Scott Lipcon committed Jun 16, 2016
Commits on Jun 7, 2016
  1. perms: make '-c' required for batch mode

    quoth Tony:
    >   Typing ^C at a command to make it stop without doing anything is a natural
    >   reaction, regardless of any imprecations to type "cancel"
    He asked for a '-b' option; i.e., don't allow a bare "ssh git@... perms repo"
    to be interpreted as batch mode.
    Meanwhile, '-c' is acceptable for existing repos too (as you can see from the
    mirroring code at least).
    So, just think of '-c' as a moral eqvt of '-b' that already exists.
    committed Jun 7, 2016
Commits on May 19, 2016
  1. rewrite create command

    create no longer calls the perms command, but creates the repo itself.
    There is some code duplication, but less dependencies between the commands.
    (With minor modifications by committer)
    skoslowski committed with Apr 12, 2016
Commits on May 7, 2016
  1. don't run postupdate unless master has been pushed

    thanks to Joseph Huttner for the idea
    gitolite tester committed with May 6, 2016
Commits on Mar 25, 2016
  1. minor install/test suite change

    perl no longer likes it when you increment a string (where you only care about
    the number at the start).  It does it anyway, but it produces a warning, and
    gitolite's install script does not like that.
    committed Mar 25, 2016
Commits on Mar 21, 2016
  1. oops; minor bug in tproxy

    thanks to Robin Johnson for catching this.
    Note it only happens in one very very specific case: when no command is sent
    by the user at all (i.e., "ssh git@host", so even if you don't have this
    patch, the workaround is "ssh git@host info");
    committed Mar 21, 2016
Commits on Feb 22, 2016
  1. oops! perl version need not be that high; remove 'use' line

    (thanks for Johnson Earls for catching this!)
    committed Feb 22, 2016
Commits on Feb 20, 2016
  1. v3.6.5

    committed Feb 20, 2016
Commits on Feb 18, 2016
  1. Add support for Github's new TEMPLATE features

    Github recently added support for TEMPLATEs for certain Github-specific
    activities, including creating Issues and Pull Requests. This patch
    creates these files as symlinks to the CONTRIBUTING document, which
    explains the process that should be used.
    Signed-off-by: Eugene E. Kashpureff Jr <>
    Committer's note: I still refuse to use pull requests that *require me to go
    to the website and do stuff there*.  But it seems it's easy enough if the
    requestor gives you a number.  In this case, it was
        git fetch github refs/pull/78/head
        git merge FETCH_HEAD
    EugeneKay committed with Feb 18, 2016
Commits on Feb 14, 2016
  1. ban repo name ending in ".git"

    'user.html' says:
        The ".git" at the end is optional for git commands (i.e., you can use
        "testing.git" instead of "testing" for clone, fetch, push, etc., if you
        like) but gitolite commands in general will not like the additional ".git"
        at the end.
    Until now, we've been catching this trailing ".git" in various commands and
    such, but there are so many programs, it's hard to make sure they all do this
    This patch catches it deep inside gitolite core.
    (based on patch sent by Paul Sokolovsky)
    pfalcon committed with Feb 13, 2016
Commits on Feb 6, 2016
  1. 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
    Oh well... so be it!
    To use, just add
        option bypass-creator-check = 1
    to the rules for the repo.
    committed Feb 6, 2016
Commits on Jan 21, 2016
Commits on Jan 20, 2016
  1. sshkeys-lint: remove a couple of subs...

    a couple of subs are now re-defined following 285c4b5 ("sshkeys-lint: use new
    ssh fingerprint functions") because that commit pulls in  One (dbg)
    was subtly different but was not being used anyway, while the other (usage)
    was genuinely redundant.  Got rid of both.
    committed Jan 20, 2016
Commits on Jan 19, 2016
  1. ukm: use new ssh fingerprint functions.

    UKM was never updated for new-style fingerprints at all.
    Signed-off-by: Robin H. Johnson <>
    robbat2 committed with Jan 13, 2016
  2. sskm: use new ssh fingerprint functions.

    SSKM was never updated for new-style fingerprints at all.
    Signed-off-by: Robin H. Johnson <>
    robbat2 committed with Jan 13, 2016
  3. sshkeys-lint: use new ssh fingerprint functions.

    Signed-off-by: Robin H. Johnson <>
    robbat2 committed with Jan 13, 2016
  4. ssh-authkeys: use new ssh fingerprint functions.

    Signed-off-by: Robin H. Johnson <>
    robbat2 committed with Jan 13, 2016