🔧 MAINTAIN: Update GitHub organisation

Author: chrisjsewell

.github/workflows/tests.yml

@@ -45,7 +45,7 @@ jobs:
       run: |
         pytest --cov=markdown_it --cov-report=xml --cov-report=term-missing
     - name: Upload to Codecov
-      if: matrix.python-version == 3.7 && github.repository == 'ExecutableBookProject/markdown-it-py'
+      if: matrix.python-version == 3.7 && github.repository == 'executablebooks/markdown-it-py'
       uses: codecov/codecov-action@v1
       with:
         name: markdown-it-py-pytests-py3.7

README.md

@@ -87,14 +87,14 @@ Big thanks to the authors of [markdown-it]:
 
 Also [John MacFarlane](https://github.com/jgm) for his work on the CommonMark spec and reference implementations.
 
-[github-ci]: https://github.com/ExecutableBookProject/markdown-it-py/workflows/Python%20package/badge.svg?branch=master
-[github-link]: https://github.com/ExecutableBookProject/markdown-it-py
+[github-ci]: https://github.com/executablebooks/markdown-it-py/workflows/Python%20package/badge.svg?branch=master
+[github-link]: https://github.com/executablebooks/markdown-it-py
 [pypi-badge]: https://img.shields.io/pypi/v/markdown-it-py.svg
 [pypi-link]: https://pypi.org/project/markdown-it-py
 [conda-badge]: https://anaconda.org/conda-forge/markdown-it-py/badges/version.svg
 [conda-link]: https://anaconda.org/conda-forge/markdown-it-py
-[codecov-badge]: https://codecov.io/gh/ExecutableBookProject/markdown-it-py/branch/master/graph/badge.svg
-[codecov-link]: https://codecov.io/gh/ExecutableBookProject/markdown-it-py
+[codecov-badge]: https://codecov.io/gh/executablebooks/markdown-it-py/branch/master/graph/badge.svg
+[codecov-link]: https://codecov.io/gh/executablebooks/markdown-it-py
 [black-badge]: https://img.shields.io/badge/code%20style-black-000000.svg
 [black-link]: https://github.com/ambv/black
 

docs/architecture.md

@@ -51,7 +51,7 @@ The difference is simple:
 - There are special token objects, "inline containers", having nested tokens.
   sequences with inline markup (bold, italic, text, ...).
 
-See [token class](https://github.com/ExecutableBookProject/markdown-it-py/tree/master/markdown_it/token.py)
+See [token class](https://github.com/executablebooks/markdown-it-py/tree/master/markdown_it/token.py)
 for details about each token content.
 
 In total, a token stream is:
@@ -69,8 +69,8 @@ to an AST.
 
 More details about tokens:
 
-- [Renderer source](https://github.com/ExecutableBookProject/markdown-it-py/tree/master/markdown_it/renderer.py)
-- [Token source](https://github.com/ExecutableBookProject/markdown-it-py/tree/master/markdown_it/token.py)
+- [Renderer source](https://github.com/executablebooks/markdown-it-py/tree/master/markdown_it/renderer.py)
+- [Token source](https://github.com/executablebooks/markdown-it-py/tree/master/markdown_it/token.py)
 - [Live demo](https://markdown-it.github.io/) - type your text and click `debug` tab.
 
 
@@ -96,7 +96,7 @@ and tried to do something yourself. We never reject with help to real developers
 
 ## Renderer
 
-After the token stream is generated, it's passed to a [renderer](https://github.com/ExecutableBookProject/markdown-it-py/tree/master/markdown_it/renderer.py).
+After the token stream is generated, it's passed to a [renderer](https://github.com/executablebooks/markdown-it-py/tree/master/markdown_it/renderer.py).
 It then plays all the tokens, passing each to a rule with the same name as token type.
 
 Renderer rules are located in `md.renderer.rules[name]` and are simple functions
@@ -172,9 +172,9 @@ This was mentioned in [Data flow](#data-flow), but let's repeat sequence again:
 
 And somewhere between you can apply additional transformations :) . Full content
 of each chain can be seen on the top of
-[parser_core.py](https://github.com/ExecutableBookProject/markdown-it-py/tree/master/markdown_it/parser_core.py),
-[parser_block.py](https://github.com/ExecutableBookProject/markdown-it-py/tree/master/markdown_it/parser_block.py) and
-[parser_inline.py](https://github.com/ExecutableBookProject/markdown-it-py/tree/master/markdown_it/parser_inline.py)
+[parser_core.py](https://github.com/executablebooks/markdown-it-py/tree/master/markdown_it/parser_core.py),
+[parser_block.py](https://github.com/executablebooks/markdown-it-py/tree/master/markdown_it/parser_block.py) and
+[parser_inline.py](https://github.com/executablebooks/markdown-it-py/tree/master/markdown_it/parser_inline.py)
 files.
 
-Also you can change output directly in [renderer](https://github.com/ExecutableBookProject/markdown-it-py/tree/master/markdown_it/renderer.py) for many simple cases.
+Also you can change output directly in [renderer](https://github.com/executablebooks/markdown-it-py/tree/master/markdown_it/renderer.py) for many simple cases.

docs/using.md

@@ -203,7 +203,7 @@ nested_tokens[0]
 
 +++
 
-After the token stream is generated, it's passed to a [renderer](https://github.com/ExecutableBookProject/markdown-it-py/tree/master/markdown_it/renderer.py).
+After the token stream is generated, it's passed to a [renderer](https://github.com/executablebooks/markdown-it-py/tree/master/markdown_it/renderer.py).
 It then plays all the tokens, passing each to a rule with the same name as token type.
 
 Renderer rules are located in `md.renderer.rules` and are simple functions

setup.py

@@ -16,7 +16,7 @@ def get_version():
     description="Python port of markdown-it. Markdown parsing, done right!",
     long_description=open("README.md").read(),
     long_description_content_type="text/markdown",
-    url="https://github.com/ExecutableBookProject/markdown-it-py",
+    url="https://github.com/executablebooks/markdown-it-py",
     project_urls={"Documentation": "https://markdown-it-py.readthedocs.io"},
     author="Chris Sewell",
     author_email="[email protected]",