Skip to content
Find file
Fetching contributors…
Cannot retrieve contributors at this time
164 lines (113 sloc) 5.05 KB

% specifying "git-config" keys and values

include sidebar-toc

@@gray((Original version thanks to teemu dot matilainen at iki dot fi.))@@

Note: this won't work unless the rc file has the right settings; please see $GIT_CONFIG_KEYS in the [rc file doc][rc].

basic syntax

The syntax is simple:

config sectionname.keyname = value

For example:

.#! conf/vim-color repo gitolite config hooks.mailinglist = gitolite-commits@example.tld config hooks.emailprefix = "[gitolite] " config = "" .end

This does either a plain "git config section.key value" (for the first 2 examples above) or "git config --unset-all section.key" (for the last example). Other forms of the git config command (--add, the value_regex, etc) are not supported.

@@red(an important warning about deleting a config line)@@

WARNING: simply deleting the config line from the conf/gitolite.conf file will not delete the variable from repo.git/config. You have to use the syntax in the last example to make gitolite execute a --unset-all operation on the given key.

substituting the repo name and the creator name

You can also use the special values %GL_REPO and %GL_CREATOR in the string. The former is available to all repos, while the latter is only available to [wild][] repos.

.#! conf/vim-color repo foo bar baz config hooks.mailinglist = %GL_REPO-commits@example.tld config hooks.emailprefix = "[%GL_REPO] " .end

overriding config values {#override_conf}

You can repeat the 'config' line as many times as you like, and the last occurrence will be the one in effect. This allows you to override settings just for one project, as in this example:

.#! conf/vim-color repo @all config hooks.mailinglist = %GL_REPO-commits@example.tld config hooks.emailprefix = "[%GL_REPO] "

# ... later ...

repo customer-project
    # different mailing list
    config hooks.mailinglist = announce@customer.tld


The "delete config variable" syntax can also be used, if you wish:

.#! conf/vim-color repo secret # no emails for this one please config hooks.mailinglist = "" config hooks.emailprefix = "" .end

As you can see, the general idea is to place the most generic ones (repo @all, or repo regex like repo foo.*) first, and place more specific ones later to override the generic settings.

compensating for UNSAFE_PATT {#unsafe-patt}

An important feature in gitolite is that you can share the admin load with more people, without having to give all of them shell access on the server. Thus there are some restrictions designed to prevent someone who can push the gitolite-admin repo, from somehow managing to run arbitrary commands on the server.

This section is about one of these restrictions.

Gitolite, by default, does not allow the following characters in the value of a config variable: ` ~ # $ & ( ) | ; < >. This is due to unspecified paranoia; see this discussion for some context. This restriction is enforced by a regex called UNSAFE_PATT, whose default value is [`~#\$\&()|;<>].

But let's say you need to do this, which fails due to the semicolon.

.#! conf/vim-color config hooks.showrev = "git show -C %s; echo" .end

There are two ways to fix this.

If all your admins already have shell access, you can override this by placing a modified version in the rc file. For our example, you'd just put the following line at the very end of your rc file, just before the 1; line (notice there is no semicolon in the regex here):

$UNSAFE_PATT          = qr([`~#\$\&()|<>]);

Similarly, you can remove other characters from that regex (to allow those characters in your config values).

If all your admins do not have shell access, you need a more fine-grained method:

  • In the rc file, add the following within the '%RC' hash (for example, just after the UMASK line would do fine):

    SAFE_CONFIG => {
        SHOWREV         =>  "git show -C %s; echo"
  • In your gitolite.conf file, add this instead of the line we saw earlier:

.#! conf/vim-color config hooks.showrev = %SHOWREV .end

This mechanism allows you to add any number of specific violations to the UNSAFE_PATT rule instead of denaturing the regex itself and potentially allowing something that could be (ab)used by a repo admin to obtain shell access at some later point in time.

A similar problem arises with email addresses, which contain the < and > characters. Here's how to deal with that easily:

  • In the rc file:

    SAFE_CONFIG => {
        LT              =>  '<',
        GT              =>  '>',
  • In the gitolite.conf file:

.#! conf/vim-color config hooks.mailinglist = "Sitaram Chamarty" .end

Admittedly, that looks a wee bit ugly, but it gets the job done without having to remove angle brackets from UNSAFE_PATT.

Something went wrong with that request. Please try again.