Fix script to programatically identify gecko-dev commit given a mozilla-central mercurial release tag
context
- in tor-browser#40857 (closed) i incorrectly based a new geckoview-99.0b3-11.5-1 based off of commit 50c4d412dbb2e6ae0ba2ab4ffc699a4614ebca8f in a cinnabar-derrived local clone of the beta branch of the mozilla-dentral mercurial repo, which had the (correct)
FIREFOX_99_0b3_BUILD1
tag
- as a result, we introduced several GB worth of commit history into our branch and lost the ability to match git commits 1:1 with the
gecko-dev
git clone of the mercurial repo
- to fix that, we manually identified the commit hashes that matched
- we would prefer to run a script generated by @sysrqb to match the mozilla-central/mercurial commit hash to the git/gecko-dev commit hash. however, when i try to run that script it errors in ways i cannot understand
- this is a ticket to hold conversation about fixing that error (see details in conversation)