Docs: Replace Poetry with Hatch (#68)

Author: BeyondEvil

.github/workflows/publish.yml

@@ -1,34 +1,31 @@
-name: publish
+name: Publish
 
 on:
   push:
     tags:
-      - v*
+      - "[0-9]+.[0-9]+.[0-9]+"
+      - "[0-9]+.[0-9]+.[0-9]+rc[0-9]+"
 
 jobs:
   publish:
+    if: github.repository == 'pytest-dev/pytest-base-url'
     runs-on: ubuntu-latest
     steps:
     - uses: actions/checkout@v3
-    - name: Set up Python
-      uses: actions/setup-python@v3
       with:
-        python-version: "3.9"
-    - name: Install poetry
-      run: curl -sSL https://install.python-poetry.org | python3 -
-    - name: Configure poetry
-      run: poetry config virtualenvs.in-project true
-    - name: Set up cache
-      uses: actions/cache@v3
+        fetch-depth: 0
+        persist-credentials: false
+
+    - name: Build and Check Package
+      uses: hynek/build-and-inspect-python-package@v1
+
+    - name: Download Package
+      uses: actions/download-artifact@v3
+      with:
+        name: Packages
+        path: dist
+
+    - name: Publish package to PyPI
+      uses: pypa/gh-action-pypi-publish@release/v1
       with:
-        path: .venv
-        key: venv-${{ hashFiles('**/poetry.lock') }}
-        restore-keys: venv-
-    - name: Install Dependencies
-      run: poetry install
-    - name: Publish
-      run: >-
-        poetry publish
-        --build
-        --username __token__
-        --password ${{ secrets.PYPI_TOKEN }}
+        password: ${{ secrets.PYPI_TOKEN }}

README.rst

@@ -169,8 +169,10 @@ the ``config`` object. This can be used to read/add/modify the metadata:
 .. code-block:: python
 
   def pytest_configure(config):
-    from pytest_metadata.plugin import metadata_key
-    config.stash[metadata_key]['foo'] = 'bar'
+    metadata = config.pluginmanager.getplugin("metadata")
+    if metadata:
+        from pytest_metadata.plugin import metadata_key
+        config.stash[metadata_key]['foo'] = 'bar'
 
 Plugin integrations
 -------------------

development.rst

@@ -1,18 +1,17 @@
 Development
 ===========
 
-To contribute to `pytest-metadata` you can use `Poetry <https://python-poetry.org/>`_ to manage
+To contribute to `pytest-metadata` you can use `Hatch <https://hatch.pypa.io/latest/>`_ to manage
 a python virtual environment and `pre-commit <https://pre-commit.com/>`_ to help you with
 styling and formatting.
 
 To setup the virtual environment and pre-commit, run:
 
 .. code-block:: bash
 
-  $ poetry install
-  $ poetry run pre-commit install
+  $ hatch -e test run pre-commit install
 
-If you're not using ``Poetry``, to install ``pre-commit``, run:
+If you're not using ``Hatch``, to install ``pre-commit``, run:
 
 .. code-block:: bash
 
@@ -30,14 +29,14 @@ Running Tests
 -------------
 
 You will need `Tox <https://tox.wiki/en/latest/>`_ installed to run the tests
-against the supported Python versions. If you're using ``Poetry`` it will be
+against the supported Python versions. If you're using ``Hatch`` it will be
 installed for you.
 
-With ``Poetry``, run:
+With ``Hatch``, run:
 
 .. code-block:: bash
 
-  $ poetry run tox
+  $ hatch -e test run tox
 
 Otherwise, to install and run, do:
 
@@ -57,6 +56,6 @@ Follow these steps to release a new version of the project:
 #. Commit and push the new branch and then create a new pull request
 #. Wait for tests and reviews and then merge the branch
 #. Once merged, update your local master again (``git pull --rebase upstream master``)
-#. Tag the release with the new release version (``git tag v<new tag>``)
+#. Tag the release with the new release version (``git tag <new tag>``)
 #. Push the tag (``git push upstream --tags``)
 #. Done.