clone releases/comm-release to releases/comm-esr78
Categories
(Developer Services :: Mercurial: hg.mozilla.org, task)
Tracking
(Not tracked)
People
(Reporter: rjl, Assigned: sheehan)
References
Details
Attachments
(1 file)
(deleted),
text/x-phabricator-request
|
Details |
Please clone the default branch of comm-beta to releases/comm-esr78. The configuration should be the same as comm-esr68.
Thanks
Assignee | ||
Updated•4 years ago
|
Assignee | ||
Comment 1•4 years ago
|
||
Adds the new comm-esr78
to the WSGI config and to some of
the repo list in mozautomation
.
Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/f7f4d53b22af
repos: add comm-esr78
to various configs r=zeid
Comment 3•4 years ago
|
||
Looks like we had a bit of a miscommunication -- would it be possible to re-create the comm-esr78 repo but based on the current comm-release and include all branches, not just the default?
When trying to merge over changes the current automation is stopping me from pushing older release branches since they no longer conform to our guidelines.
(As an aside -- I hope that this is essentially the same process used for mozilla-esr78, but I don't know if that's documented.)
Comment 4•4 years ago
|
||
Note that we haven't used comm-esr78 at all yet, so anything that's currently there can be thrown away.
Comment 5•4 years ago
|
||
FWIW, l10n cross-channel doesn't like the comm-esr78 isn't a fork of comm-release.
We don't care about branches, though.
Marking as blocking bug 1649420, as that has to wait at least for the comm-esr78 repo to be "not thrown away".
Updated•4 years ago
|
Assignee | ||
Comment 6•4 years ago
|
||
Sure, I'll re-clone comm-esr78
from comm-release
instead and include all branches.
Assignee | ||
Comment 7•4 years ago
|
||
Should be good to go.
Comment 8•4 years ago
|
||
Thank you Connor! I confirmed I was able to push the necessary changes!
Description
•