Run pre-commit hooks #204

Author: Ludee

.github/ISSUE_TEMPLATE/issue_template_feature.md

@@ -3,7 +3,7 @@ name: Feature Issue
 about: For new ideas, developments and features
 title: Your title should make sense if said after "The issue is <your issue title>"
 labels: ["status: active :construction:", "type: feature :hammer_and_wrench:"]
-assignees: ''
+assignees: ""
 ---
 
 ## Description of the issue

.github/ISSUE_TEMPLATE/issue_template_release.md

@@ -9,7 +9,7 @@ labels:
     "type: release :rocket:",
     "part: github :octocat:",
   ]
-assignees: 'Ludee'
+assignees: "Ludee"
 ---
 
 ## Description of the release

.github/ISSUE_TEMPLATE/issue_template_user_kudos.md

@@ -2,22 +2,21 @@
 name: User Kudos Issue
 about: User Community - Give kudos to the project
 title: Add new user to USERS.cff
-labels: 
+labels:
   [
     "other: good first issue :seedling:",
     "priority: low :sloth:",
     "type: enhancement :gear:",
     "part: community :earth_africa:",
   ]
-assignees: ''
-
+assignees: ""
 ---
 
 I thank the developers of the project. <br>
 Please add my information to the file [USERS.cff](https://github.com/rl-institut/super-repo/blob/production/USERS.cff).
 
-family-names: 
-given-names: 
-alias: 
-affiliation: 
-orcid: 
+family-names:
+given-names:
+alias:
+affiliation:
+orcid:

.github/pull_request_template.md

@@ -19,6 +19,7 @@ Describe the findings of the discussion in the issue or meeting.
 ## Workflow checklist
 
 ### Automation
+
 Part of # / Closes #
 
 ### PR-Assignee

.github/workflows/codecov.yml

@@ -3,7 +3,7 @@
 
 name: codecov
 
-on: 
+on:
   push:
     branches: [ production, develop ]
 

LICENSES/BSD-2-Clause.txt

@@ -1,4 +1,4 @@
-Copyright (c) <year> <owner> 
+Copyright (c) <year> <owner>
 
 Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met:
 

LICENSES/MIT.txt

@@ -17,4 +17,4 @@ IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS
 FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR
 COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER
 IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN
-CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
+CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

RELEASE_PROCEDURE.md

@@ -195,6 +195,5 @@ If you messed up, remove tags and start again
 
 - https://raw.githubusercontent.com/folio-org/stripes/master/doc/release-procedure.md
 
-
 !!! note "Used Icons"
     🐙 GitHub | 💠 git | 📝 File | 💻 Command Line

docs/code/install/index.md

@@ -2,7 +2,7 @@
 
 ## Environment (Conda)
 
-With conda, you can create, export, list, remove, and update environments 
+With conda, you can create, export, list, remove, and update environments
 that have different versions of Python and/or packages installed in them. <br>
 Switching or moving between environments is called activating the environment.
 You can also share an environment file and import from `requirements.txt`.
@@ -11,23 +11,20 @@ You can also share an environment file and import from `requirements.txt`.
 💻 `activate py310` Activate environment <br>
 💻 `python --version` Check python version
 
-
 ## Requirements
 
-In Python the `requirements.txt` file helps manage dependencies. 
+In Python the `requirements.txt` file helps manage dependencies.
 It's a text file that lists the packages that the Python project depends on.
 
 💻 `pip install -r requirements.txt` Install from file
 
-
 ## Pyproject
 
-This python package contains a `pyproject.toml` file that contains 
-build system requirements and information, which are 
-[used by pip](https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/) 
+This python package contains a `pyproject.toml` file that contains
+build system requirements and information, which are
+[used by pip](https://pip.pypa.io/en/stable/reference/build-system/pyproject-toml/)
 to build the package.
 It contains the metadata of the software project.
 
-
 !!! note "Used Icons"
     🐙 GitHub | 💠 git | 📝 File | 💻 Command Line

docs/development/collaboration/license_and_citation.md

@@ -1,16 +1,15 @@
 # License
 
-
 ## Software License
 
 This software is developed under an
 [open-source license](https://en.wikipedia.org/wiki/Open-source_license). <br>
 The selected license can be read in the
 [LICENSE.txt](https://github.com/rl-institut/super-repo/blob/production/LICENSE.txt).
 
-This repository follows the [REUSE SOFTWARE](https://reuse.software/) 
-specification. 
-All files are explicitly stating the corresponding license and copyright information. 
+This repository follows the [REUSE SOFTWARE](https://reuse.software/)
+specification.
+All files are explicitly stating the corresponding license and copyright information.
 It is implemented as GitHub workflow and pre-commit hook:
 
 - GitHub workflow: [reuse.yml](https://github.com/rl-institut/super-repo/blob/feature-7-REUSE/.github/workflows/reuse.yml)

docs/development/collaboration/meeting.md

@@ -3,7 +3,7 @@
 In order to develop a program collaboratively, it is helpful to regularly
 exchange information about the current status and to discuss open questions
 and make decisions. <br>
-If you want to join the meetings, please use the 
+If you want to join the meetings, please use the
 [GitHub Discussions](https://github.com/rl-institut/super-repo/discussions).
 
 ## Developer Meetings

docs/development/collaboration/users.md

@@ -1,5 +1,5 @@
 # Users
 
-Known user of this software can be added to 
-[USERS.cff](https://github.com/rl-institut/super-repo/blob/production/USERS.cff) 
+Known user of this software can be added to
+[USERS.cff](https://github.com/rl-institut/super-repo/blob/production/USERS.cff)
 for reference.