summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorNed Batchelder <ned@nedbatchelder.com>2018-06-23 16:53:25 -0400
committerNed Batchelder <ned@nedbatchelder.com>2018-06-23 20:00:08 -0400
commit036de87ddda41e960760efe0024e8045c8a9cdc6 (patch)
tree909cf924dc669f5b5b442a5ad85d3478c17d3a92
parent05fd9d8ffdd9abea83ffa01eabffbccad0f1eb77 (diff)
downloadpython-coveragepy-git-036de87ddda41e960760efe0024e8045c8a9cdc6.tar.gz
Update docs to point to GitHubcoverage-4.5.1a
-rw-r--r--doc/contributing.rst11
-rw-r--r--doc/faq.rst11
-rw-r--r--doc/index.rst10
-rw-r--r--doc/trouble.rst2
4 files changed, 13 insertions, 21 deletions
diff --git a/doc/contributing.rst b/doc/contributing.rst
index 656d2519..3f628109 100644
--- a/doc/contributing.rst
+++ b/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/
diff --git a/doc/faq.rst b/doc/faq.rst
index f6085b61..a0145362 100644
--- a/doc/faq.rst
+++ b/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
diff --git a/doc/index.rst b/doc/index.rst
index 20658edd..44e53946 100644
--- a/doc/index.rst
+++ b/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.
diff --git a/doc/trouble.rst b/doc/trouble.rst
index 7534c5cb..e3951218 100644
--- a/doc/trouble.rst
+++ b/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