That’s a read-only mirror, not a “move onto GitHub”.
PRs get automatically closed, referring to the contrib docs.
It’s sad that an entity the importance and the size of Mozilla chose GitHub over self-hosting. It’s insane they were still using Mercurial in 2025.
It’s insane they were still using Mercurial in 2025.
What?
What what? Mercurial is dead. Not even Facebook use it any more.
Dead? They just had a major version update 1 month ago and the last minor release was 1 week ago.
What does Facebook using it have to do with anything?
Dead as in essentially nobody uses it. Apparently it’s used even less than SVN, which sounds kind of crazy. Doesn’t stop them developing it if they want I guess.
Facebook is relevant because they were one of the last major users of Mercurial and were big contributors to it. They’ve moved to their own VCS Sapling now though.
What’s the actual argument here? If Mercurial satisfies/satisfied the development team, then they should use it. I don’t find this crazy. Like others pointed out, it’s not like Mercurial was a dead project without maintenance.
No developer is an island. By using an extremely unpopular VSC they increase the barrier to contribution for all external developers, miss out on support in tools and projects that only support Git, and they don’t get to benefit from the increased development effort that goes into more popular solutions.
They aren’t moving, it’s a code mirror. Everyone seems to be misreporting this. There’s a GitHub action to auto close PRs.
It’s not a mirror. It’s the primary repository. And yes unfortunately they aren’t accepting PRs or using it for issue tracking, but it’s a start.
That’s very good. Once I wanted to compile Firefox myself for some reason I no longer remember, but their Mercurial-based system was a hassle to work with. Most of us are already familiar with git. So, I know I’m going to be more inclined to make code contributions now that it uses git.
Just wish they could’ve chosen another git-based option like Codeberg, or even an internally-hosted server. I’m rather wary of GitHub/Microsoft swallowing up so many open source projects.
Seems that they’re not accepting pull-requests via GitHub, which is a bit of shame.
For a complicated project I get it, github’s PR system is kind of bad (horrible branch based workflow and no stacked diff support resulting in increased churn) compared to the alternatives.
That’s why we have tools like Graphite to add stacked diff support on top of github, and other devs creating new VCSs because git still hasn’t made it’s interactive rebase and merge conflicts easy enough to handle for juniors and it should be simpler.