Prepare for release (#86)

* Update README.md

* Update README.md

* Update test.yaml

* [pre-commit.ci] auto fixes from pre-commit.com hooks

for more information, see https://pre-commit.ci

---------

Co-authored-by: pre-commit-ci[bot] <66853113+pre-commit-ci[bot]@users.noreply.github.com>

.github/workflows/test.yaml

@@ -32,8 +32,6 @@ jobs:
           --verbose
     - name: Upload coverage to Codecov
       uses: codecov/codecov-action@v3
-      with:
-        token: ${{ secrets.CODECOV_TOKEN }}
 
   ruff:
     runs-on: ubuntu-latest

README.md

@@ -1,16 +1,15 @@
 # CMI-DAIR Template Python Repository
 
-This is a template repository. Below is a checklist of things you should do to use it:
+Welcome to the CMI-DAIR Template Python Repository! This template is designed to streamline your project setup and ensure a consistent structure. To get started, follow these steps:
 
-- [ ] Run `setup_template.py` to set up the repository.
-- [ ] Rewrite this `README` file.
-- [ ] Install the `pre-commit` hooks.
-- [ ] Update the `LICENSE` file to your desired license and set the year.
-- [ ] Update the supported versions in `SECURITY.md` or, if not relevant, delete this file.
+
+- [ ] Run `setup_template.py` to initialize the repository.
+- [ ] Replace the content of this `README.md` with details specific to your project.
+- [ ] Install the `pre-commit` hooks to ensure code quality on each commit.
+- [ ] Revise SECURITY.md to reflect supported versions or remove it if not applicable.
 - [ ] Remove the placeholder src and test files, these are there merely to show how the CI works.
-- [ ] Grant third-party app permissions (e.g. Codecov) [here](https://github.com/organizations/cmi-dair/settings/installations), if necessary.
-- [ ] Either generate a `CODECOV_TOKEN` secret [here](https://github.com/cmi-dair/flowdump/blob/main/.github/workflows/python_tests.yaml) (if its a private repository) or remove the line `token: ${{ secrets.CODECOV_TOKEN }}`
-- [ ] API docs website: After the first successful build, go to the `Settings` tab of your repository, scroll down to the `GitHub Pages` section, and select `gh-pages` as the source. This will generate a link to your API docs.
+- [ ] If it hasn't already been done for your organization/acccount, grant third-party app permissions for CodeCov.
+- [ ] To set up an API documentation website, after the first successful build, go to the `Settings` tab of your repository, scroll down to the `GitHub Pages` section, and select `gh-pages` as the source. This will generate a link to your API docs.
 - [ ] Update stability badge in `README.md` to reflect the current state of the project. A list of stability badges to copy can be found [here](https://github.com/orangemug/stability-badges). The [node documentation](https://nodejs.org/docs/latest-v20.x/api/documentation.html#documentation_stability_index) can be used as a reference for the stability levels.
 
 # Project name