Please create a releases/mozilla-esr78 repository, cloned from the current mozilla-beta tip.

Hooks and settings should be like releases/mozilla-esr68 . Please document enabled hooks and access controls in this bug when enabled.

(In reply to Justin Wood (:Callek) from comment #0)

Please create a releases/mozilla-esr78 repository, cloned from the current mozilla-beta tip.

Hooks and settings should be like releases/mozilla-esr68 . Please document enabled hooks and access controls in this bug when enabled.

Sounds good.

Is this bug supposed to be employee-confidential?

So the repo is replicated to the mirrors.

Add the repo to the hgweb.config so it appears on hgmo,
Add to the bundle-repos file so we have clone bundles available.
Configure commits from esr78 to appear in mozilla-unified and
add to mozautomation so various other scripts are aware of it.

Depends on D76847

(In reply to Connor Sheehan [:sheehan] from comment #1)

Is this bug supposed to be employee-confidential?

I see no reason on my end that it should be, if the patches attached are public-ok feel free to open it up.

Pushed by cosheehan@mozilla.com:
https://hg.mozilla.org/hgcustom/version-control-tools/rev/2306f875c201
ansible/hg-web: add esr78 to mirror filters r=zeid
https://hg.mozilla.org/hgcustom/version-control-tools/rev/64ce416fefc6
ansible: add esr78 to various configs r=zeid

Repo is created at https://hg.mozilla.org/releases/mozilla-esr78

The following hooks are enabled:

• push printurls (ie "click here to see your push on treeherder" etc)
• prevent bookmarks
• treeclosure
• single head per branch
• prevent NSPR NSS changes

Along with all other globally activated hooks. Configuration is essentially identical to ESR68.

Permissions are set to scm_allow_direct_push.

Please ping me if something looks wrong with the configuration. Cheers!