move setup.cfg to pyproject.toml

Author: sjvrijn

CHANGELOG.md

@@ -11,6 +11,7 @@
 
 ### Changed
 
+* Moved from setup.cfg/.py to pyproject.toml [#351](https://github.com/NLeSC/python-template/issues/351)
 * Moved from prospector to ruff [#336](https://github.com/NLeSC/python-template/issues/336)
 * Renamed `project_name` to `directory_name` in cookiecutter questionnaire
 * Initial linting is error free [#227](https://github.com/NLeSC/python-template/issues/227)

hooks/pre_gen_project.py

@@ -6,5 +6,6 @@
     "directory_name": cookiecutter.directory_name.lower().replace(" ", "-"),
     "full_name": cookiecutter.full_name.replace('\"', '\\\"'),
     "repository": "git@github.com:" + cookiecutter.github_organization + "/" + cookiecutter.directory_name.lower().replace(" ", "-"),
+    "repository_url": "https://github.com/" + cookiecutter.github_organization + "/" + cookiecutter.directory_name.lower().replace(" ", "-"),
     "package_short_description": cookiecutter.package_short_description.replace('\"', '\\\"')
 }) }}

{{cookiecutter.directory_name}}/.github/next_steps/01_sonarcloud_integration.md

@@ -4,7 +4,7 @@ title: 'Next step: Sonarcloud integration'
 
 Continuous code quality can be handled by [Sonarcloud](https://sonarcloud.io/). This repository is configured to use Sonarcloud to perform quality analysis and code coverage report on each push.
 
-In order to configure Sonarcloud analysis [GitHub Action workflow]({{cookiecutter.repository}}/blob/main/.github/workflows/sonarcloud.yml) you must follow the steps below:
+In order to configure Sonarcloud analysis [GitHub Action workflow]({{cookiecutter.repository_url}}/blob/main/.github/workflows/sonarcloud.yml) you must follow the steps below:
 
 1. go to [Sonarcloud](https://sonarcloud.io/projects/create) to create a new Sonarcloud project
 1. login with your GitHub account

{{cookiecutter.directory_name}}/.github/next_steps/02_citation.md

@@ -2,7 +2,7 @@
 title: 'Next step: Citation data'
 ---
 
-It is likely that your `CITATION.cff` currently doesn't pass validation. The error messages you get from the [`cffconvert`]({{cookiecutter.repository}}/actions/workflows/cffconvert.yml) GitHub Action are unfortunately a bit cryptic, but doing the following helps:
+It is likely that your `CITATION.cff` currently doesn't pass validation. The error messages you get from the [`cffconvert`]({{cookiecutter.repository_url}}/actions/workflows/cffconvert.yml) GitHub Action are unfortunately a bit cryptic, but doing the following helps:
 
 - [ ] Check if the `given-name` and `family-name` keys need updating. If your family name has a name particle like `von` or `van` or `de`, use the `name-particle` key; if your name has a suffix like `Sr` or `IV`, use `name-suffix`. For details, refer to the schema description: https://github.com/citation-file-format/citation-file-format
 - [ ] Update the value of the `orcid` key. If you do not have an orcid yet, you can get one here [https://orcid.org/](https://orcid.org/).
@@ -14,7 +14,7 @@ It is likely that your `CITATION.cff` currently doesn't pass validation. The err
 Once you do all the steps above, the `cffconvert` workflow will tell you what content it expected to see in `.zenodo.json`. Copy-paste from the GitHub Action log into a new file `.zenodo.json`. Afterwards, the `cffconvert` GitHub Action should be green.
 
 
-To help you keep the citation metadata up to date and synchronized, the [`cffconvert`]({{cookiecutter.repository}}/actions/workflows/cffconvert.yml) GitHub Action checks the following 6 aspects:
+To help you keep the citation metadata up to date and synchronized, the [`cffconvert`]({{cookiecutter.repository_url}}/actions/workflows/cffconvert.yml) GitHub Action checks the following 6 aspects:
 
 1. Whether your repository includes a `CITATION.cff` file.
 

{{cookiecutter.directory_name}}/.github/next_steps/03_readthedocs.md

@@ -15,6 +15,6 @@ To host the documentation of this repository please perform the following instru
       2. make sure {{ cookiecutter.github_organization }} has been granted access.
       3. reload repository list on Read the Docs import page
 1. wait for the first build to be completed at <https://readthedocs.org/projects/{{ cookiecutter.directory_name }}/builds>
-1. check that the link of the documentation badge in the [README.md]({{ cookiecutter.repository }}) works
+1. check that the link of the documentation badge in the [README.md]({{ cookiecutter.repository_url }}) works
 
-See [README.dev.md#]({{cookiecutter.repository}}/blob/main/README.dev.md#generating-the-api-docs) how to build documentation site locally.
+See [README.dev.md#]({{cookiecutter.repository_url}}/blob/main/README.dev.md#generating-the-api-docs) how to build documentation site locally.

{{cookiecutter.directory_name}}/.github/next_steps/04_zenodo_integration.md

@@ -8,7 +8,7 @@ To enable Zenodo integration:
 
 1. Go to http://zenodo.org and login with your GitHub account. When you are redirected to GitHub, *Authorize application* to give permission to Zenodo to access your account.
 1. Go to <https://zenodo.org/account/settings/github/> and enable Zenodo integration of your repository by clicking on `On` toggle button.
-2. Your package will get a DOI only after you make a release. Create a new release as described in [README.dev.md]({{cookiecutter.repository}}/blob/main/README.dev.md#33-github)
+2. Your package will get a DOI only after you make a release. Create a new release as described in [README.dev.md]({{cookiecutter.repository_url}}/blob/main/README.dev.md#33-github)
 3. At this point you should have a DOI. To find out the DOI generated by Zenodo:
    1. Visit https://zenodo.org/deposit and click on your repository link
    2. You will find the latest DOI in the right column in Versions box in **Cite all versions?** section

{{cookiecutter.directory_name}}/.github/next_steps/05_linting.md

@@ -2,9 +2,9 @@
 title: 'Next step: Linting'
 ---
 
-Your repository has a [workflow]({{ cookiecutter.repository }}/blob/main/.github/workflows/build.yml) which [lints](https://en.wikipedia.org/wiki/Lint_(software)) your code after every push and when creating a pull request.
+Your repository has a [workflow]({{ cookiecutter.repository_url }}/blob/main/.github/workflows/build.yml) which [lints](https://en.wikipedia.org/wiki/Lint_(software)) your code after every push and when creating a pull request.
 
-Linter workflow may fail if `description` or `keywords` field in [setup.cfg]({{ cookiecutter.repository }}/blob/main/setup.cfg) is empty. Please update these fields. To validate your changes run:
+Linter workflow may fail if `description` or `keywords` field in [setup.cfg]({{ cookiecutter.repository_url }}/blob/main/setup.cfg) is empty. Please update these fields. To validate your changes run:
 
 ```shell
 ruff .

{{cookiecutter.directory_name}}/CITATION.cff

@@ -10,7 +10,7 @@ authors:
 date-released: 20??-MM-DD
 doi: <insert your DOI here>
 version: "{{ cookiecutter.version }}"
-repository-code: "{{ cookiecutter.repository }}"
+repository-code: "{{ cookiecutter.repository_url }}"
 keywords:
   - {{ cookiecutter.keyword1 }}
   - {{ cookiecutter.keyword2 }}

{{cookiecutter.directory_name}}/CONTRIBUTING.md

@@ -13,13 +13,13 @@ The sections below outline the steps in each case.
 
 ## You have a question
 
-1. use the search functionality [here]({{cookiecutter.repository}}/issues) to see if someone already filed the same issue;
+1. use the search functionality [here]({{cookiecutter.repository_url}}/issues) to see if someone already filed the same issue;
 2. if your issue search did not yield any relevant results, make a new issue;
 3. apply the "Question" label; apply other labels when relevant.
 
 ## You think you may have found a bug
 
-1. use the search functionality [here]({{cookiecutter.repository}}/issues) to see if someone already filed the same issue;
+1. use the search functionality [here]({{cookiecutter.repository_url}}/issues) to see if someone already filed the same issue;
 1. if your issue search did not yield any relevant results, make a new issue, making sure to provide enough information to the rest of the community to understand the cause and context of the problem. Depending on the issue, you may want to include:
     - the [SHA hashcode](https://help.github.com/articles/autolinked-references-and-urls/#commit-shas) of the commit that is causing your problem;
     - some identifying information (name and version number) for dependencies you're using;

{{cookiecutter.directory_name}}/README.dev.md

@@ -203,4 +203,4 @@ twine upload dist/*
 
 ### (3/3) GitHub
 
-Don't forget to also make a [release on GitHub]({{cookiecutter.repository}}/releases/new). If your repository uses the GitHub-Zenodo integration this will also trigger Zenodo into making a snapshot of your repository and sticking a DOI on it.
+Don't forget to also make a [release on GitHub]({{cookiecutter.repository_url}}/releases/new). If your repository uses the GitHub-Zenodo integration this will also trigger Zenodo into making a snapshot of your repository and sticking a DOI on it.