<aside> ⚠️

Wichtig: Bitte Commit Messages so formattieren:

https://www.conventionalcommits.org/en/v1.0.0/ — commit message types

https://cbea.ms/git-commit/ — write good commit messages

</aside>

• english naming
• use snake_case for branch names, database fields, and identifiers where applicable
• keep functions and classes small and focused
• one function should do one thing
• avoid duplicated code
• write comments only when they add real value
• remove unused code, debug code, and commented-out code before comitting
• use consistent formatting
• uniform error handling approach
• keep PRs small and focused
• document important technical decisions and non-obvious logic

Testing

Code Formatting

• The best way is to put a shared .editorconfig file in the project repo. IntelliJ supports EditorConfig, and JetBrains documents that you can export your current code style to an .editorconfig file from Editor → Code Style → Scheme actions → Export → EditorConfig File.
  • For unified formatting across all team devices
  • shared formatting rules are stored in .editorconfig
  • IntelliJ should use EditorConfig support
  • run Reformat Code before committing
  • formatting rules in the repository are the team standard