I believe the best tool for the job is the hg-git Mercurial plugin. Toolsįirst of all, we have to choose the tools we want to use for this migration. So I thought I’d explain how I did it, and point out the issues I ran into. There are various ways to do it, and various sources that give you half-baked solutions using half-baked tools. I suppose the most obvious choice is to migrate them to Git repositories on Bitbucket. You need to manually convert your repositories. Now, given such a decision, it would have been nice if Bitbucket had offered an automatic migration service, but alas, there is no such thing. #TORTOISEHG CLONE LOCAL REPOSITORY CODE#So basically you *have* to migrate your Mercurial repositories before June 1st 2020, or else you lose your code and history forever. They will no longer allow you to create new Mercurial repositories starting February 1st 2020, and by June 2020, they will shut down Mercurial access altogether, and what’s worse: they will *delete* all your existing Mercurial repositories. However, Git appears to have won the battle in the end, and this has triggered Bitbucket to stop supporting Mercurial repositories. Using TortoiseHg on Windows was very straightforward and reliable.Īs a result, all of my repositories that I have created on Bitbucket over the years, have been Mercurial ones. My preferred source control system has always been Mercurial (Hg), especially in those early days, when I found the tools for Git on Windows to be quite unstable and plagued with compatibility issues. I have been a long-time user of Bitbucket for my personal projects, over 10 years now, I believe.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |