Bookhoard/bookhoard
0
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases 12 Wiki Activity

docs: add code indentation guideline to project standards

Browse Source 
Add explicit guideline specifying 2-space indentation for all code files
unless the language prohibits it. This ensures consistent formatting across
the entire codebase and prevents debates about tab vs space preferences.

The guideline is placed in the General section alongside other coding
convention rules to maintain consistency in project standards.
This commit is contained in:
john-okeefe
2026-02-27 16:57:41 -05:00
parent 7bae42bb11
commit 6562b20ee5
1 changed files with 1 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
PROJECT_GUIDELINES.md
+1
View File
@@ -55,6 +55,7 @@
- Run `git push` and wait for completion - Run `git push` and wait for completion
- Never use `&&` to chain git commands together - Never use `&&` to chain git commands together
- ✅ **Make good organized git commits for the entire project (not just what you changed) and push - run git add, commit, push sequentially as separate commands, no need to repeatedly check status** - ✅ **Make good organized git commits for the entire project (not just what you changed) and push - run git add, commit, push sequentially as separate commands, no need to repeatedly check status**
- ✅ **Indentation is always 2 spaces unless the language prohibits it**
### Cascading Fix-up Pattern (PROHIBITED) ### Cascading Fix-up Pattern (PROHIBITED)