Bugzilla

(In reply to Rob Lemley [:rjl] from comment #5)
> We do have https://github.com/thunderbird/comm-unified-l10n, which looks funny on the main branch but does have comm-central, comm-beta, comm-release, comm-esr128, and comm-esr115. It's updated daily via scheduled GH action using git-cinnabar. I suppose that it could be modified to run via webhook or something so it's always current.

To clarify what I poorly phrased for  "normalized into a single git tree" wasn't about having all the branches in a single repo, although that is nice to have.  My concern is I would want the "mozilla/" subdirectory to be present in the same git tree as "mail/".  That doesn't have to be a public tree that people can check-out, it could be something synthetically generated locally by the searchfox indexers and propagated between indexing runs (which is what already happens for the source and blame trees, although the source trees usually do correspond to a public tree at this point).

(In reply to Rob Lemley [:rjl] from comment #5)
> We do have https://github.com/thunderbird/comm-unified-l10n, which looks funny on the main branch but does have comm-central, comm-beta, comm-release, comm-esr128, and comm-esr115. It's updated daily via scheduled GH action using git-cinnabar. I suppose that it could be modified to run via webhook or something so it's always current.

To clarify what I poorly phrased for  "normalized into a single git tree" wasn't about having all the branches in a single repo, although that is nice to have.  My concern is I would want the "mozilla/" subdirectory to be present in the same git tree as "mail/".  That doesn't have to be a public tree that people can clone, it could be something synthetically generated locally by the searchfox indexers and propagated between indexing runs (which is what already happens for the source and blame trees, although the source trees usually do correspond to a public tree at this point).