From: reuben.popp at gmail.com (Reuben Popp)
Subject: Nesting repositories under a common folder?
Date: Wed, 24 Jul 2019 14:05:38 -0500 [thread overview]
Message-ID: <CAB-aZK-r2ogA_qfe6Muz08C12DHYReT1o=dd_7Sbua7c3yzoYA@mail.gmail.com> (raw)
Thanks for the reply John,
how else would I collapse reposection classes?
On Wed, Jul 24, 2019 at 1:45 PM John Keeping <john at keeping.me.uk> wrote:
> On Wed, Jul 24, 2019 at 01:01:27PM -0500, Reuben Popp wrote:
> > Excuse me if this has been answered before, but is there a way to nest
> > repositories under a common directory visually in cgit?
> > For example,
> > root_directory (not a repo)
> > |- Project A (directory, not a repo)
> > | |- Project A component 1 (repo)
> > | |- Project A component 2 (repo)
> > |- Project B (repo)
> > |- Project C (directory, not a repo)
> > | |- Project C subproject AA (repo)
> > | |- Project C subproject AB (repo)
> > | |- Project C Archive (directory, not a repo)
> > | |- Project C archived subproject A (repo)
> > etc.
> > Going to the cgit frontend, I would see the directories (or links) for
> > Project A, B and C...
> You can't do exactly this, but you can generate sections from the path
> to the repository which adds headings to the list of repositories. See
> "section" and "section-from-path" in cgitrc(5).
> For hierarchical paths, it's also possible to view a subset of the tree
> by going to (for example) /cgit/directory_a/directory_b/ but I don't
> think anything generates links to those sublists.
> I remember in the past somewhere had added a custom script to collapse
> sections by default, but I can't find a reference for that now. That
> should be reasonably simple by matching on the "reposection" class.
-------------- next part --------------
An HTML attachment was scrubbed...
next prev parent reply other threads:[~2019-07-24 19:05 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-24 18:01 reuben.popp
2019-07-24 18:40 ` list
2019-07-24 18:43 ` john
2019-07-24 19:05 ` reuben.popp [this message]
2019-07-24 19:44 ` john
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).