From 2fb773adc5e37add4b2db802d7fe9921bddbcf3c Mon Sep 17 00:00:00 2001 From: Philipp Emanuel Weidmann Date: Mon, 17 Aug 2026 15:12:34 +0530 Subject: [PATCH] chore: remove Gemini style guide --- .gemini/styleguide.md | 11 ----------- 1 file changed, 11 deletions(-) delete mode 100644 .gemini/styleguide.md diff --git a/.gemini/styleguide.md b/.gemini/styleguide.md deleted file mode 100644 index 88d23d1..0000000 --- a/.gemini/styleguide.md +++ /dev/null @@ -1,11 +0,0 @@ -# Style guide and coding conventions - -* Identifier names should not contain abbreviations unless those abbreviations are very widely used and understood (e.g. "KL divergence"). -* Comments should start with a capital letter and end with a period. They should use correct grammar and spelling. -* Function and method signatures **must** be fully type-annotated, including the return type (if any). -* Every Python code file **must** start with an SPDX/Copyright header. -* Settings descriptions should start with a capital letter and end with a period. -* When new settings are added in `config.py`, they should also be added to `config.default.toml`, set to their default value and with their description as a comment. The order of settings in `config.default.toml` should match that in `config.py`. -* Pull requests should implement one change, and one change only. - * PRs containing multiple semantically independent changes **must** be split into multiple PRs. - * PRs **must not** change existing code unless the changes are *directly related* to the PR. This includes changes to formatting and comments.