From 38b78b0d2b95022a570ef3a9c0830f033792e658 Mon Sep 17 00:00:00 2001 From: amagan Date: Tue, 22 Sep 2026 11:08:02 +0200 Subject: [PATCH 1/2] docs: remove empty Development section in CONTRIBUTING Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com> --- CONTRIBUTING.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index 4d0f613..dc38279 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -44,5 +44,3 @@ project's structure or architecture. and its purpose. - Be sure to link the corresponding issue in your pull request to maintain proper tracking of contributions. - Remember to add license and copyright information following the [REUSE Specification](https://reuse.software/spec/#copyright-and-licensing-information). - -## Development From 6e9aa083cba9150401f921f81a0dca5d4502875c Mon Sep 17 00:00:00 2001 From: amagan Date: Tue, 22 Sep 2026 12:15:12 +0200 Subject: [PATCH 2/2] docs: fix 'recommend to use' -> 'recommend using' in CONTRIBUTING --- CONTRIBUTING.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/CONTRIBUTING.md b/CONTRIBUTING.md index dc38279..a3b3c27 100644 --- a/CONTRIBUTING.md +++ b/CONTRIBUTING.md @@ -39,7 +39,7 @@ to avoid duplications and unnecessary discussions. This will help coordinate efforts and prevent conflicts. - It is always advisable to discuss and gather feedback from the community before making significant changes to the project's structure or architecture. -- Ensure a clean and organized commit history. Divide your changes into logical and descriptive commits. We recommend to use the [Conventional Commits Specification](https://www.conventionalcommits.org/en/v1.0.0/) +- Ensure a clean and organized commit history. Divide your changes into logical and descriptive commits. We recommend using the [Conventional Commits Specification](https://www.conventionalcommits.org/en/v1.0.0/) - Document any new changes or features you add. This will help other contributors and project users understand your work and its purpose. - Be sure to link the corresponding issue in your pull request to maintain proper tracking of contributions.