Feature #27479
Feature #27365: Gitweb configuration
manage description throughout forge/gerrit/git
| Status: | Accepted | Start date: | 2011-06-15 | |
|---|---|---|---|---|
| Priority: | Should have | Due date: | ||
| Assignee: | Peter Niederlag | % Done: | 0% |
|
| Category: | - | |||
| Target version: | - | |||
| Votes: | 1 (View) |
Description
find a nice way to manage the description line of forge/gerrit/git.
Related issues
History
Updated by Peter Niederlag about 2 years ago
- Subject changed from manage description throughou forge/gerrit/git to manage description throughout forge/gerrit/git
Updated by Peter Niederlag about 2 years ago
forge description field seems to be the one I'd favore. gitweb.description will be cut after 25 chars by default putting the rest into the title tag
Updated by Peter Niederlag about 2 years ago
- Tracker changed from Bug to Feature
Updated by Nicole Cordes about 1 year ago
Not sure, but normaly a description can be provided by description file in .git folder for gitweb.
Updated by Steffen Gebert about 1 year ago
Yes, can be retrieved from forge: http://forge.typo3.org/projects/typo3v4-core.json
Updated by Jacob Floyd about 1 month ago
Is there a way for gitweb (git.typo3.org) to get the .git/description file from gerrit? If so, then someone would just need to have permission to edit descriptions here:
https://review.typo3.org/#/admin/projects/
(If you want a volunteer to go through and add descriptions to all of the projects, count me in.)
Do we really have to keep forge and gerrit project descriptions in sync? At a minimum, git.typo3.org should show something more useful than: Unnamed repository; edit this file to name it for gitweb. And if the forge description is so much longer, then it wouldn't be very useful in gitweb thanks to truncation, right?
I think we need one description for gitweb/gerrit, and a separate one for forge.
We could have a post-receive hook that copies a .description file in each repo (or processes composer.json) to extract the project description and put it in .git/description (as mentioned on stackoverflow1)
[1] http://stackoverflow.com/questions/3214871/git-push-git-description-file
Updated by Steffen Gebert about 1 month ago
Hi Jacob,
thanks for your investigations. Indeed I see the problem in the forge description being to short. Two thoughts:
- let people set the description in Gerrit, retrieve this via the API and write it to the `.git/description` file
- finally drop gitweb and spend some time on using GitBlit together with the GitBlit plugin for Gerrit. I just gave it a quick try: https://dev.review.typo3.org.REMOVE_ME/plugins/gitblit/ (URL might be broken in some days). There's still a problem that subrepos can't be opened and it looks like descriptions are also not there. But IMHO that's the way to go..
I'm in favour of the latter one, but couple of tasks are higher prio. But still, will ask on the Gerrit list, why it doesn't work for us.