Update location of beancount repository

The beancount repository moved to GitHub recently.

.appveyor.yml

@@ -14,7 +14,7 @@ install:
   - cd C:\projects\%APPVEYOR_PROJECT_NAME%
   - cpanm --notest --installdeps .
   - set PATH=%PYTHON%;%PYTHON%\\Scripts;%PATH%
-  - python -m pip install -U hg+https://bitbucket.org/blais/beancount/
+  - python -m pip install -U git+https://github.com/beancount/beancount/
 
 build_script:
   - cd tests

.travis.yml

@@ -7,10 +7,10 @@ python:
   - "3.6"
 env:
   - BEANCOUNT="beancount>=2.1.2"
-  - BEANCOUNT="hg+https://bitbucket.org/blais/beancount/"
+  - BEANCOUNT="git+https://github.com/beancount/beancount/"
 matrix:
   allow_failures:
-  - env: BEANCOUNT="hg+https://bitbucket.org/blais/beancount/"
+  - env: BEANCOUNT="git+https://github.com/beancount/beancount/"
 addons:
   apt:
     packages:

docs/changelog.md

@@ -5,6 +5,7 @@
 * Show warning for unknown `apply` directive
 * Recognize `apply rate` directive (an alias of `apply fixed`)
 * Don't convert meta-data on ignored virtual postings but keep as comments
+* Update location of beancount repository
 
 ## 2.1 (2020-04-06)
 

docs/manual.md

@@ -8,7 +8,7 @@ author:
     - Stefano Zacchiroli
     - Martin Michlmayr
 keywords: ledger, beancount, conversion, accounting, bookkeeping
-date: April 2020
+date: May 2020
 documentclass: scrartcl
 urlcolor: blue
 toc: true
@@ -161,7 +161,7 @@ of beancount, but some functionality may require an unreleased version of
 beancount.  You can install the latest development version of beancount
 directly from the beancount repository:
 
-    pip3 install hg+https://bitbucket.org/blais/beancount/
+    pip3 install git+https://github.com/beancount/beancount/
 
 Currently, there are no features that require an unreleased version of
 beancount.
@@ -261,7 +261,7 @@ If you use commas as the decimal separator (i.e. values like `10,12`,
 using the ledger option `--decimal-comma`) you have to set the
 `decimal_comma` option to `true`.  Please note that commas are not
 supported as the decimal separator in beancount at the moment ([issue
-204](https://bitbucket.org/blais/beancount/issues/204)) so your
+204](https://github.com/beancount/beancount/issues/204)) so your
 amounts are converted not to use comma as the decimal separator.
 
 Commas as separators for thousands (e.g. `1,000,000`) are supported by
@@ -293,7 +293,7 @@ character will be replaced with an `X` if it's not a letter and the
 same will be done for the last character if it's not a letter or digit.
 Finally, all beancount commodities currently have to consist of at least
 two characters ([issue
-192](https://bitbucket.org/blais/beancount/issues/192)).
+192](https://github.com/beancount/beancount/issues/192)).
 
 If you require a mapping between ledger and beancount commodities, you
 can use `commodity_map`.  You can use your ledger commodity names or
@@ -482,7 +482,7 @@ but you should make sure the values are valid in beancount.
 
 Beancount allows tags for transactions but currently doesn't support
 tags for postings ([issue
-144](https://bitbucket.org/blais/beancount/issues/144)).  Because of
+144](https://github.com/beancount/beancount/issues/144)).  Because of
 this, posting-level tags are currently stored as metadata with the key
 `tags`.  This should be seen as a workaround because metadata with the
 key `tags` is not treated the same way by beancount as proper tags.
@@ -553,15 +553,15 @@ would become the following in beancount:
 Comments are supported.
 
 Currently, beancount doesn't accept top-level comments with the `|` marker
-([issue 282](https://bitbucket.org/blais/beancount/issues/282)).
+([issue 282](https://github.com/beancount/beancount/issues/282)).
 ledger2beancount changes such comments to use the `;` marker.
 
 
 ## Virtual costs
 
 Beancount does not have a concept of [virtual
 costs](https://www.ledger-cli.org/3.0/doc/ledger3.html#Virtual-posting-costs)
-([issue 248](https://bitbucket.org/blais/beancount/issues/248)).
+([issue 248](https://github.com/beancount/beancount/issues/248)).
 ledger2beancount therefore treats them as regular costs (or, rather,
 as regular prices).