Adding a description to a non-wild repo

[G. Drukier]

I would like to provide descriptions for my managed, non-wild repos, so that running the info -ld command will remind my users what each one is for. But I haven't been able to figure out how to do it.

I tried the desc command, but that only seems to work for wild repos.

I tried adding a desc = "This is the description" line in gitolite.conf, but then I got this returned on the push.

remote: FATAL: git config 'gitweb.description' not allowed
remote: check GIT_CONFIG_KEYS in the rc file

I tried adding gitweb.description into GIT_CONFIG_KEYS in the .gitolite.rc file and that removed the error, but info -ld still didn't have a description. I'm not actually using gitweb, so I'd rather not go to the bother of installing it just to be able to add a description field.

Adding a description file directly to the repo on the gitolite server seems to work, but is there any other way to do this?

I'm running: gitolite3 v3.6.2-13-ge79f335 on git 1.9.3

[Sitaram Chamarty]

Uggh; that's a bug in 'info'. Will fix this weekend; sorry about that!

(It should be getting it from the gitweb.description config variable, not from the description file!)

[milk]

I would still like to have the ability to use a description file. With
the way we define repos in our conf file and the number of repos we
have, it would be ugly to define a gitweb.description for each repo.

> --
> You received this message because you are subscribed to the Google Groups "gitolite" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to gitolite+u...@googlegroups.com.
> For more options, visit https://groups.google.com/d/optout.



--
Hope is a dimension of the spirit. It is not outside us, but within
us. When you lose it, you must seek it again within yourself and in
people around you -- not in objects or even events. -
-Vaclav Havel

[Sitaram Chamarty]

On 01/30/2015 10:01 AM, milk wrote:
> I would still like to have the ability to use a description file. With
> the way we define repos in our conf file and the number of repos we
> have, it would be ugly to define a gitweb.description for each repo.

I was going to use both actually; if gitweb.description is found, use that, else 'description' file.

sitaram

[G Drukier]

> On Jan 30, 2015, at 00:06, Sitaram Chamarty <sita...@gmail.com> wrote:
>
> On 01/30/2015 10:01 AM, milk wrote:
>> I would still like to have the ability to use a description file. With
>> the way we define repos in our conf file and the number of repos we
>> have, it would be ugly to define a gitweb.description for each repo.
>
> I was going to use both actually; if gitweb.description is found, use that, else 'description' file.

If I’m understanding things, the options are to add a gitweb.description via a "desc =“ entry in gitolite.conf, or to add a description file. The latter needs to be added into the server repo itself by logging in to the gitolite account. I.e. it can’t be done via pushes from gitolite-admin. Nor can it come from clones of the repo, since the file lives within the .git directory and isn’t a pushable file. Do I have this all correct?

[Sitaram Chamarty]

You were asking about the 'info' command's ability to print the
description in response to the '-ld' option, if I recall.

The info command currently looks at the 'description' file. However,
gitolite's conf syntax ("desc = foo bar baz") puts this in
$BARE_REPO.git/config as the variable gitweb.description.

I will now make 'info' look in both places (gitweb.description takes
preference over 'description' file).

Now, as for actually adding a description, what you want *can* be done.
You need to enable 'cgit' (in the rc file). If you see the comments at
the top of src/triggers/post-compile/update-description-file you will
understand why I say this.

BUT... there's a caveat. That code has a problem and I have not yet
pushed the change. This also will be done by the weekend.

HTH