chore(deps): bump from template

Author: helmut-hoffer-von-ankershoffen

.copier-answers.yml

@@ -1,4 +1,4 @@
-_commit: v0.5.12
+_commit: v0.5.13
 _src_path: gh:helmut-hoffer-von-ankershoffen/oe-python-template
 author_email: helmuthva@gmail.com
 author_github_username: helmut-hoffer-von-ankershoffen

.github/copilot-instructions.md

@@ -1,4 +1,4 @@
-Always conform to the coding styles defined in CODE-STYLE.md in the root
+Always conform to the coding styles defined in CODE_STYLE.md in the root
 directory of this repository when generating code.
 
 Learn about tools to use in CONTRIBUTING.md in the root directory of this

.vscode/settings.json

@@ -57,7 +57,7 @@
     "github.copilot.chat.edits.temporalContext.enabled": true,
     "github.copilot.chat.codeGeneration.instructions": [
         {
-            "file": "CODE-STYLE.md"
+            "file": "CODE_STYLE.md"
         },
         {
             "file": "CONTRIBUTING.md"

CODE-STYLE.md CODE_STYLE.mdCODE-STYLE.md renamed to CODE_STYLE.md

@@ -1,19 +1,10 @@
----
-title: Code Style
-author: Helmut Hoffer von Ankershoffen (@helmut-hoffer-von-ankershoffen)
-audience: all
-status: draft
-created: 2025-03-16
-updated: 2025-03-16
-tags: [style, code, python, typescript]
-description: |
-  This document describes the code style used in [oe-python-template](https://github.com/helmut-hoffer-von-ankershoffen/oe-python-template) and derivatives. It defines
-  strict requirements to be followed by all contributors - humans and agents - to
-  ensure consistency and readability across the codebase.
----
-
 # Code Style
 
+Author: Helmut Hoffer von Ankershoffen (@helmut-hoffer-von-ankershoffen )
+Status: Draft
+Created: 2025-03-16
+Updated: 2025-03-16
+
 This document describes the code style used in
 [oe-python-templat](https://github.com/helmut-hoffer-von-ankershoffen/oe-python-template)
 and derivatives. It defines strict requirements to be followed by all
@@ -121,8 +112,6 @@ We generate the final documentation using Sphinx and publish it to readthedocs.
 We use [pytest](https://docs.pytest.org/en/stable/) for testing Python code.
 
 - Tests are defined in the `tests/` directory
-- Tests are named test__.py and classes are named Test_
-- Test functions are named test_*
 - We use pytest fixtures to set up test data and state
 - We leverage several pytest plugins:
   - `pytest-asyncio` for testing async code

CONTRIBUTING.md

@@ -139,7 +139,7 @@ uv run nox -s update_from_template
 
 ## Pull Request Guidelines
 
-- Before starting to write code read the [CODE-STYlE.md](CODE-STYLE.md) document for mandatory coding style
+- Before starting to write code read the [code style guide](CODE_STYLE.md) document for mandatory coding style
   guidelines.
 - **Pre-Commit Hooks:** We use pre-commit hooks to ensure code quality. Please install the pre-commit hooks by running `uv run pre-commit install`. This ensure all tests, linting etc. pass locally before you can commit.
 - **Squash Commits:** Before submitting a pull request, please squash your commits into a single commit.

SECURITY.md

@@ -49,9 +49,9 @@ We follow these security best practices:
 
 We promote security awareness among contributors and users
 
-- We indicate security as a priority in our mandatory
-  [CODE-STYLE.md](CODE-STYLE.md) document, to be followed by human and agentic
-  contributors.
+- We indicate security as a priority in our
+  [code style guide](CODE_STYLE.md), to be followed by human and agentic
+  contributors as mandatory
 - We publish our security posture in SECURITY.md (this document), encouraring
   users to report vulnerabilities.
 

docs/source/code-style.rst

@@ -0,0 +1 @@
+.. mdinclude:: ../../CODE_STYLE.md

docs/source/index.rst

@@ -14,9 +14,10 @@
    api_v1
    api_v2
    reference
-   release-notes
    security
+   release-notes
    contributing
+   code-style
 
 .. sidebar-links::
    :caption: Links