Coverage.py is on GitHub

Sunday 24 June 2018

After many years on Bitbucket, today I moved coverage.py development to GitHub. I’ve long wanted to use Git instead of Mercurial, but I didn’t want to lose the issues that were on Bitbucket.

I thought GitHub issues were the simplest possible bug tracker. But I realized that Bitbucket’s were even simpler: they have no labels. So I bit the bullet, added some features to the Bitbucket issue migration tool, and switched over.

There had been a GitHub mirror of the code, but I started a new repo so that the issues transferred from Bitbucket could keep their old numbers. The old mirror is still around, because there’s a handful of issues and pull requests there that I didn’t want to lose.

This move is also a kind of way to declare some pull request bankruptcy. I’ve embodied the bad habit of letting pull requests languish, sometimes for years. I shouldn’t let that happen, but I can’t promise that I will do better. I’ll try. At least Git will give me a more familiar environment in which to work with them, which I hope will help.

Another side-effect of making a new repo is that I have hardly any stars yet...

Comments

[gravatar]
Ed Davies 7:52 AM on 25 Jun 2018

Just curious, but why do you want to use Git instead of Mercurial? Is there a reason other than “because everybody else does”?

I picked Mercurial just before it became obvious that Git would be the most used (a sort of Betamax decision). I'm trying to see an advantage to Git which would motivate me put up with its messy user interface (https://xkcd.com/1597/).

[gravatar]
Ned Batchelder 11:14 AM on 25 Jun 2018

@Ed: Code in git feels more malleable to me than in Mercurial. Whether that's because of inherent differences or familiarity differences, I don't know.

[gravatar]
Wooble 11:59 AM on 25 Jun 2018

I've always thought BitBucket's lack of features in the issue tracker was an entirely deliberate way to try to get you to buy Jira. GitHub's tracker may not be all that great, but at least they're not clearly deliberately making it bad because they want to sell you something else.

[gravatar]
Aron Griffis 6:31 PM on 25 Jun 2018

@Wooble Right, I've seen Atlassian close feature requests with the rationale that they're reserving features for "Bitbucket's big brother Jira." Since then I've preferred GitHub or GitLab over Bitbucket.

Add a comment:

Ignore this:
Leave this empty:
Name is required. Either email or web are required. Email won't be displayed and I won't spam you. Your web site won't be indexed by search engines.
Don't put anything here:
Leave this empty:
URLs auto-link and some tags are allowed: <a><b><i><p><br><pre>.