Open
Bug 1504811
Opened 6 years ago
Updated 6 years ago
Load per-repository hgrc files from version-control-tools
Categories
(Developer Services :: Mercurial: hg.mozilla.org, enhancement)
Developer Services
Mercurial: hg.mozilla.org
Tracking
(Not tracked)
NEW
People
(Reporter: gps, Unassigned)
Details
Currently, a handful of repositories on hg.mozilla.org have custom .hg/hgrc config files. These define hooks, extra extensions, etc.
This model is not robust because:
a) you need filesystem access to see what modifications have been made
b) you need filesystem access to modify hgrc files
c) no mechanism to view history of hgrc files over time
I'd like to vendor these custom hgrc files into version-control-tools and have an extension inject them into per-repo configs as if the content came from the .hg/hgrc file itself.
This "solves" the above issues. One downside is it will require a deploy in order for production to pick up hgrc changes. But I think that's an acceptable price to pay for the benefits it would provide.
Reporter | ||
Comment 1•6 years ago
|
||
While this is certainly doable with existing Mercurial, https://phab.mercurial-scm.org/D5221 will make this much easier to implement. Assuming it lands, it will first appear in the release of Mercurial after 4.8. Presumably 4.9.
Comment 2•6 years ago
|
||
Perhaps it would also be useful to expose this information via the `repoinfo` web command[0]. So far we only export the `scm_level_X` group that is required to make changes to the repo, this feels like something that would be useful there as well. Just a thought. :)
[0] https://hg.mozilla.org/hgcustom/version-control-tools/repoinfo
You need to log in
before you can comment on or make changes to this bug.
Description
•