Pull in 4.5.1a changes to update docs for GitHub migration.

Author: nedbat

doc/contributing.rst

@@ -19,7 +19,7 @@ One source of history or ideas are the `bug reports`_ against coverage.py.
 There you can find ideas for requested features, or the remains of rejected
 ideas.
 
-.. _bug reports: https://bitbucket.org/ned/coveragepy/issues?status=new&status=open
+.. _bug reports: https://github.com/nedbat/coveragepy/issues
 
 
 Before you begin
@@ -35,8 +35,8 @@ you frustration.
 Getting the code
 ----------------
 
-The coverage.py code is hosted on a `Mercurial`_ repository at
-https://bitbucket.org/ned/coveragepy.  To get a working environment, follow
+The coverage.py code is hosted on a GitHub repo at
+https://github.com/nedbat/coveragepy.  To get a working environment, follow
 these steps:
 
 #.  (Optional, but recommended) Create a virtualenv to work in, and activate
@@ -47,7 +47,7 @@ these steps:
 
 #.  Clone the repo::
 
-        $ hg clone https://bitbucket.org/ned/coveragepy
+        $ git clone https://github.com/nedbat/coveragepy
         $ cd coveragepy
 
 #.  Install the requirements::
@@ -174,10 +174,9 @@ Contributing
 ------------
 
 When you are ready to contribute a change, any way you can get it to me is
-probably fine.  A pull request on Bitbucket is great, but a simple diff or
+probably fine.  A pull request on GitHub is great, but a simple diff or
 patch works too.
 
 
 .. _editorconfig.org: http://editorconfig.org
-.. _Mercurial: https://www.mercurial-scm.org/
 .. _tox: https://tox.readthedocs.io/

doc/faq.rst

@@ -127,14 +127,9 @@ mailing list.
 
 .. _Testing In Python: http://lists.idyll.org/listinfo/testing-in-python
 
-Bug reports are gladly accepted at the `Bitbucket issue tracker`_.
+Bug reports are gladly accepted at the `GitHub issue tracker`_.
 
-.. _Bitbucket issue tracker: https://bitbucket.org/ned/coveragepy/issues
-
-Announcements of new coverage.py releases are sent to the
-`coveragepy-announce`_ mailing list.
-
-.. _coveragepy-announce: http://groups.google.com/group/coveragepy-announce
+.. _GitHub issue tracker: https://github.com/nedbat/coveragepy/issues
 
 `I can be reached`__ in a number of ways, I'm happy to answer questions about
 using coverage.py.
@@ -151,4 +146,4 @@ Since 2004, `Ned Batchelder`_ has extended and maintained it with the help of
 
 .. _Gareth Rees:    http://garethrees.org/
 .. _Ned Batchelder: https://nedbatchelder.com
-.. _many others:    https://bitbucket.org/ned/coveragepy/src/tip/CONTRIBUTORS.txt
+.. _many others:    https://github.com/nedbat/coveragepy/blob/master/CONTRIBUTORS.txt

doc/index.rst

@@ -180,13 +180,11 @@ coverage.py or get help using it on the `Testing In Python`_ mailing list.
 
 .. _Testing In Python: http://lists.idyll.org/listinfo/testing-in-python
 
-Bug reports are gladly accepted at the `Bitbucket issue tracker`_.
-Bitbucket also hosts the `code repository`_. There is a `mirrored repo`_ on
-GitHub.
+Bug reports are gladly accepted at the `GitHub issue tracker`_.
+GitHub also hosts the `code repository`_.
 
-.. _Bitbucket issue tracker: https://bitbucket.org/ned/coveragepy/issues
-.. _code repository: https://bitbucket.org/ned/coveragepy
-.. _mirrored repo: https://github.com/nedbat/coveragepy
+.. _GitHub issue tracker: https://github.com/nedbat/coveragepy/issues
+.. _code repository: https://github.com/nedbat/coveragepy
 
 `I can be reached`_ in a number of ways. I'm happy to answer questions about
 using coverage.py.

doc/trouble.rst

@@ -23,7 +23,7 @@ working properly.
 If your problem isn't discussed here, you can of course search the `coverage.py
 bug tracker`_ directly to see if there is some mention of it.
 
-.. _coverage.py bug tracker: https://bitbucket.org/ned/coveragepy/issues?status=new&status=open
+.. _coverage.py bug tracker: https://github.com/nedbat/coveragepy/issues
 
 
 Things that don't work