pre-commit: run prettier

Author: consideRatio

.github/workflows/docs.yml

@@ -65,5 +65,5 @@ jobs:
       - name: Publish to GitHub Pages
         if: github.ref == 'refs/heads/main'
         run: |
-            pip install ghp-import
-            ghp-import --no-jekyll --push --message "Update documentation [skip ci]" docs/_build/html
+          pip install ghp-import
+          ghp-import --no-jekyll --push --message "Update documentation [skip ci]" docs/_build/html

.github/workflows/publish.yml

@@ -7,8 +7,8 @@ name: Release
 on:
   pull_request:
     paths-ignore:
-    - "docs/**"
-    - "**/docs.yml"
+      - "docs/**"
+      - "**/docs.yml"
   push:
     paths-ignore:
       - "docs/**"

.github/workflows/test.yml

@@ -40,8 +40,8 @@ jobs:
 
       - name: Run webpack to build static assets
         run: |
-            npm install
-            npm run webpack
+          npm install
+          npm run webpack
 
       - name: Install dependencies
         run: |

CHANGELOG.md

@@ -39,15 +39,14 @@
 
 [@akhmerov](https://github.com/search?q=repo%3Ajupyterhub%2Fnbgitpuller+involves%3Aakhmerov+updated%3A2021-09-02..2022-03-18&type=Issues) | [@brian-rose](https://github.com/search?q=repo%3Ajupyterhub%2Fnbgitpuller+involves%3Abrian-rose+updated%3A2021-09-02..2022-03-18&type=Issues) | [@choldgraf](https://github.com/search?q=repo%3Ajupyterhub%2Fnbgitpuller+involves%3Acholdgraf+updated%3A2021-09-02..2022-03-18&type=Issues) | [@consideRatio](https://github.com/search?q=repo%3Ajupyterhub%2Fnbgitpuller+involves%3AconsideRatio+updated%3A2021-09-02..2022-03-18&type=Issues) | [@jameshowison](https://github.com/search?q=repo%3Ajupyterhub%2Fnbgitpuller+involves%3Ajameshowison+updated%3A2021-09-02..2022-03-18&type=Issues) | [@jdmansour](https://github.com/search?q=repo%3Ajupyterhub%2Fnbgitpuller+involves%3Ajdmansour+updated%3A2021-09-02..2022-03-18&type=Issues) | [@manics](https://github.com/search?q=repo%3Ajupyterhub%2Fnbgitpuller+involves%3Amanics+updated%3A2021-09-02..2022-03-18&type=Issues) | [@ryanlovett](https://github.com/search?q=repo%3Ajupyterhub%2Fnbgitpuller+involves%3Aryanlovett+updated%3A2021-09-02..2022-03-18&type=Issues) | [@welcome](https://github.com/search?q=repo%3Ajupyterhub%2Fnbgitpuller+involves%3Awelcome+updated%3A2021-09-02..2022-03-18&type=Issues) | [@yuvipanda](https://github.com/search?q=repo%3Ajupyterhub%2Fnbgitpuller+involves%3Ayuvipanda+updated%3A2021-09-02..2022-03-18&type=Issues) | [@Zsailer](https://github.com/search?q=repo%3Ajupyterhub%2Fnbgitpuller+involves%3AZsailer+updated%3A2021-09-02..2022-03-18&type=Issues)
 
-
 ### 1.0.2 - 2021-09-03
 
 A release to fix an issue that stopped us from publishing nbgitpuller on
 conda-forge.
 
 #### Maintenance and upkeep improvements
 
-- Fix jupyter-packaging reference, use - instead of _ [#219](https://github.com/jupyterhub/nbgitpuller/pull/219) ([@consideRatio](https://github.com/consideRatio))
+- Fix jupyter-packaging reference, use - instead of \_ [#219](https://github.com/jupyterhub/nbgitpuller/pull/219) ([@consideRatio](https://github.com/consideRatio))
 
 ### 1.0.1 - 2021-09-02
 
@@ -169,7 +168,7 @@ This is a critical security release, please upgrade to this and see [GHSA-mq5p-2
 - Add a mybinder.org tab to the link builder ([#129](https://github.com/jupyterhub/nbgitpuller/pull/129))
 - tab activation on link generator ([#132](https://github.com/jupyterhub/nbgitpuller/pull/132))
 - fixing bug ([#134](https://github.com/jupyterhub/nbgitpuller/pull/134))
-- Fix typo from ipynb link generator external tool reference  ([#136](https://github.com/jupyterhub/nbgitpuller/pull/136))
+- Fix typo from ipynb link generator external tool reference ([#136](https://github.com/jupyterhub/nbgitpuller/pull/136))
 - Use the correct branch for contentRepo ([#138](https://github.com/jupyterhub/nbgitpuller/pull/138))
 - Fix file paths or application paths ([#140](https://github.com/jupyterhub/nbgitpuller/pull/140))
 - Make the environment repo branch required for binder ([#143](https://github.com/jupyterhub/nbgitpuller/pull/143))

README.md

@@ -1,6 +1,5 @@
 # [nbgitpuller](https://github.com/jupyterhub/nbgitpuller)
 
-
 [![GitHub Workflow Status - Test](https://img.shields.io/github/workflow/status/jupyterhub/nbgitpuller/Tests?logo=github&label=tests)](https://github.com/jupyterhub/nbgitpuller/actions)
 [![CircleCI build status](https://img.shields.io/circleci/build/github/jupyterhub/nbgitpuller?logo=circleci&label=docs)](https://circleci.com/gh/jupyterhub/nbgitpuller)
 [![](https://img.shields.io/pypi/v/nbgitpuller.svg?logo=pypi)](https://pypi.python.org/pypi/nbgitpuller)
@@ -25,8 +24,7 @@ pip install nbgitpuller
 
 ## Example
 
-
-This example shows how to use the  [nbgitpuller link generator](https://jupyterhub.github.io/nbgitpuller/link)
+This example shows how to use the [nbgitpuller link generator](https://jupyterhub.github.io/nbgitpuller/link)
 to create an nbgitpuller link, which a user then clicks.
 
 1. The [nbgitpuller link generator GUI](https://jupyterhub.github.io/nbgitpuller/link) is used to create a

RELEASE.md

@@ -6,7 +6,6 @@
 These are instructions on how to make a release on PyPI.
 The PyPI release is done automatically by TravisCI when a tag is pushed.
 
-
 ## Steps to make a release
 
 1. Checkout main and make sure it is up to date.

docs/contributing.md

@@ -42,40 +42,42 @@ Hence, nbgitpuller can be developed locally without needing a JupyterHub.
    ```
 
 7. Enable the nbgitpuller extension:
-   * as a jupyter serverextension (classic Notebook Server extension)
 
-      ```bash
-      jupyter serverextension enable --sys-prefix nbgitpuller
-      ```
-   * as a jupyter server extension
-      ```bash
-      jupyter server extension enable --sys-prefix nbgitpuller
-      ```
+   - as a jupyter serverextension (classic Notebook Server extension)
+
+     ```bash
+     jupyter serverextension enable --sys-prefix nbgitpuller
+     ```
+
+   - as a jupyter server extension
+     ```bash
+     jupyter server extension enable --sys-prefix nbgitpuller
+     ```
 
 8. Start the notebook server:
 
-   * You can either start the classical Notebook server.
-   This will open the classic notebook in your web
-   browser, and automatically authenticate you as a side effect.
-
-      ```bash
-      jupyter notebook
-      ```
-
-   * Or you can start the new Jupyter Server.
-      ```bash
-      jupyter server
-      ```
-      This won't open any notebook interface, unless you don't enable one
-      ([`nbclassic`](https://github.com/jupyterlab/nbclassic) or [`jupyterlab`](https://github.com/jupyterlab/jupyterlab))
-      as a jupyter server extension.
-      ```bash
-      jupyter server extension enable --sys-prefix nbclassic
-      ```
-      or
-      ```bash
-      jupyter server extension enable --sys-prefix jupyterlab
-      ```
+   - You can either start the classical Notebook server.
+     This will open the classic notebook in your web
+     browser, and automatically authenticate you as a side effect.
+
+     ```bash
+     jupyter notebook
+     ```
+
+   - Or you can start the new Jupyter Server.
+     ```bash
+     jupyter server
+     ```
+     This won't open any notebook interface, unless you don't enable one
+     ([`nbclassic`](https://github.com/jupyterlab/nbclassic) or [`jupyterlab`](https://github.com/jupyterlab/jupyterlab))
+     as a jupyter server extension.
+     ```bash
+     jupyter server extension enable --sys-prefix nbclassic
+     ```
+     or
+     ```bash
+     jupyter server extension enable --sys-prefix jupyterlab
+     ```
 
 9. You can now test nbgitpuller locally, by hitting the `/git-pull` url with any
    of the [URL query parameters](topic/url-options.rst). For example, to pull the
@@ -87,8 +89,8 @@ Hence, nbgitpuller can be developed locally without needing a JupyterHub.
    ```
 
 10. If you make changes to nbgitpuller's python code, you need to restart the `jupyter notebook`
-   process (started in step 5) to see your changes take effect. This is not needed if
-   you are only working on the javascript or css.
+    process (started in step 5) to see your changes take effect. This is not needed if
+    you are only working on the javascript or css.
 
 ## Running the flake8 linter
 
@@ -100,7 +102,7 @@ flake8 config is in `.flake8`, and is not super strict. You should be able to ru
 
 [pytest](https://docs.pytest.org/) is used to run unit and integration tests,
 under the `tests/` directory. If you add new functionality, you should also add
-tests to cover it.  You can run the tests locally with `py.test tests/`
+tests to cover it. You can run the tests locally with `py.test tests/`
 
 ## Building documentation
 

docs/index.md

@@ -15,11 +15,13 @@ Here's an example of `nbgitpuller` in action:
    link.
 
    ```{image} _static/nbgitpuller-link-generator.png
+
    ```
 
 2. A user clicks the link, and the content is pulled into a live Jupyter session.
 
    ```{image} _static/nbgitpuller-demo.gif
+
    ```
 
 ## Use `nbgitpuller`
@@ -35,6 +37,7 @@ Here's a short overview:
 
 There are several ways to generate an `nbgitpuller` link.
 The two easiest ways to do so are:
+
 - Via a browser extension to generate links directly from your repository ([Chrome extension](https://chrome.google.com/webstore/detail/nbgitpuller-link-generato/hpdbdpklpmppnoibabdkkhnfhkkehgnc), [Firefox extension](https://addons.mozilla.org/en-US/firefox/addon/nbgitpuller-link-generator/?utm_source=addons.mozilla.org&utm_medium=referral&utm_content=search)
 - Via a GUI web-app [at `nbgitpuller.link`](http://nbgitpuller.link)
 
@@ -45,7 +48,7 @@ Fore more information about generating nbgitpuller links, see [](use.md).
 Use nbgitpuller when:
 
 1. You want an easy way to distribute content (notebooks, markdown files, etc) to Jupyter users without requiring them to use `git`.
-2. You have an alternative method for *collecting* content from your users, as `nbgitpuller` does not "push", it only "pulls".
+2. You have an alternative method for _collecting_ content from your users, as `nbgitpuller` does not "push", it only "pulls".
 
 You should **not** use nbgitpuller when:
 

docs/topic/repo-best-practices.md

@@ -4,7 +4,6 @@ Sometimes, git's flexibility can lead to repositories that cause issues
 when used with nbgitpuller. Here are some recommendations to make your
 nbgitpuller experience smoother.
 
-
 ## Never force push
 
 Never use `--force` or `--force-with-lease` when pushing to your repositories.

docs/use.md

@@ -18,9 +18,10 @@ repository is made for the student. On successive clicks, the latest version
 of the remote repository is fetched, and merged automatically with the
 student's local copy using a {ref}`series of rules <topic/automatic-merging>`
 that ensure students never get merge conflicts nor lose any of their changes.
+
 ## Create an `nbgitpuller` link via a web extension
 
-The easiest way to create an `nbgitpuller` link is via a web extension  ([github repo](https://github.com/yuvipanda/nbgitpuller-link-generator-webextension)).
+The easiest way to create an `nbgitpuller` link is via a web extension ([github repo](https://github.com/yuvipanda/nbgitpuller-link-generator-webextension)).
 This allows you to quickly generate an `nbgitpuller` link directly from the content in your repository (e.g., on GitHub).
 See the links below to download the extension.
 
@@ -37,8 +38,7 @@ This contains a simple web form where you paste the location of the content you'
 
 ## Manually create an `nbgitpuller` link
 
-
-There is a short video showing 
+There is a short video showing
 
 ```{raw} html
 <iframe