feat: Add native Git hooks for automatic code formatting (#167)

* feat: add tmux-based development setup script

- Add setup.sh script to start all services in tmux session
- Add stop.sh script for graceful shutdown
- Add comprehensive development/README.md with setup instructions
- Include prerequisite checks for Go, Node.js, npm, Docker, and tmux
- Validate environment files before starting services
- Auto-install dependencies if missing
- Update main README.md with development setup section

Fixes #155

* docs: clarify environment setup and add documentation references

- Change backend/.env to ./backend/.env to avoid confusion
- Add note about running backend in separate user environment
- Clarify sync server startup command in service URLs
- Add CCSync documentation website references in setup.sh error messages
- Add documentation link for OAuth credential setup

* feat: add Husky pre-commit hooks for automatic code formatting

- Setup Husky v9.1.7 with lint-staged for pre-commit hooks
- Automatically run Prettier on staged frontend files (JS/TS/JSON/CSS/MD)
- Automatically run gofmt on staged backend Go files
- Add .prettierignore to exclude build artifacts and dependencies
- Update CONTRIBUTING.md with Husky setup information
- Add .husky/README.md for hook documentation
- Update .gitignore to exclude node_modules and package-lock.json at root

This prevents contributors from forgetting to run formatting commands
manually, ensuring consistent code style across all commits.

Fixes: #114

* chore: update Husky pre-commit hook for v10 compatibility

Remove deprecated shebang and husky.sh sourcing to prepare for Husky v10

* refactor: replace Husky with native Git hooks

- Remove Husky dependency and root package.json
- Add setup-git-hooks.sh script for native Git hook installation
- Maintain automatic formatting functionality for frontend and backend
- Update CONTRIBUTING.md with new setup instructions

This addresses maintainer feedback to avoid adding complexity with
a root package.json. Contributors run ./scripts/setup-git-hooks.sh
once after cloning to enable automatic code formatting.

Fixes: #114

* refactor: implement automated Git hooks setup via npm postinstall

- Created .githooks/pre-commit for native Git hook implementation
- Added postinstall script to automatically configure Git hooks on npm install
- Hook runs prettier for frontend files and gofmt for backend files
- Updated documentation to reflect automated setup process
- Removed manual setup script as hooks now configure automatically

Resolves maintainer feedback to avoid root package.json complexity

Author: Hell1213

.githooks/pre-commit

@@ -0,0 +1,43 @@
+#!/bin/sh
+
+echo "Running pre-commit checks..."
+
+STAGED_FILES=$(git diff --cached --name-only --diff-filter=ACM)
+
+if [ -z "$STAGED_FILES" ]; then
+    exit 0
+fi
+
+FRONTEND_FILES=$(echo "$STAGED_FILES" | grep -E '^frontend/.*\.(js|jsx|ts|tsx|json|css|scss|md)$' || true)
+BACKEND_FILES=$(echo "$STAGED_FILES" | grep -E '^backend/.*\.go$' || true)
+
+if [ -n "$FRONTEND_FILES" ]; then
+    echo "This runs before the commit to test frontend linting!"
+    cd frontend
+    npm run pre-commit
+    if [ $? -ne 0 ]; then
+        echo "Error: Frontend formatting failed"
+        cd ..
+        exit 1
+    fi
+    cd ..
+    git add $FRONTEND_FILES
+fi
+
+if [ -n "$BACKEND_FILES" ]; then
+    if command -v gofmt >/dev/null 2>&1; then
+        echo "Formatting backend Go files with gofmt..."
+        echo "$BACKEND_FILES" | xargs gofmt -w
+        if [ $? -ne 0 ]; then
+            echo "Error: gofmt formatting failed"
+            exit 1
+        fi
+        echo "$BACKEND_FILES" | xargs git add
+    else
+        echo "Warning: gofmt not found. Skipping Go file formatting."
+        echo "Install Go to enable automatic Go formatting."
+    fi
+fi
+
+echo "Pre-commit checks completed successfully!"
+exit 0

.prettierignore

@@ -0,0 +1,20 @@
+node_modules
+dist
+build
+coverage
+.next
+.nuxt
+.cache
+.vscode
+.idea
+*.min.js
+*.min.css
+package-lock.json
+yarn.lock
+pnpm-lock.yaml
+.husky
+backend/docs/swagger.json
+backend/docs/swagger.yaml
+*.log
+.env
+.env.*

CONTRIBUTING.md

@@ -25,6 +25,7 @@ Scan through our [existing issues](https://github.com/its-me-abhishek/ccsync/iss
 1. Fork the repository.
 
 - Using GitHub Desktop:
+
   - [Getting started with GitHub Desktop](https://docs.github.com/en/desktop/installing-and-configuring-github-desktop/getting-started-with-github-desktop) will guide you through setting up Desktop.
   - Once Desktop is set up, you can use it to [fork the repo](https://docs.github.com/en/desktop/contributing-and-collaborating-using-github-desktop/cloning-and-forking-repositories-from-github-desktop)!
 
@@ -48,8 +49,18 @@ Please follow these rules or conventions while committing any new changes:
 - `refactor`: refactoring production code, eg. renaming a variable
 - `test`: adding missing tests, refactoring tests
 - `chore`: updating grunt tasks, etc., no production code change
-- Run `npx prettier --write .` before commiting so as to adhere to the linting scheme of the project's frontend
-- Run `gofmt -w .` before commiting so as to adhere to the linting scheme of the project's backend
+
+**Note:** This project uses Git pre-commit hooks to automatically format code before committing.
+
+The hooks are set up automatically when you run `npm install` in the frontend directory. When you commit changes:
+
+- Frontend files (JS/TS/JSON/CSS/MD) will be automatically formatted with Prettier
+- Backend Go files will be automatically formatted with gofmt (if Go is installed)
+
+If you need to manually format files:
+
+- Run `npm run pre-commit` for frontend formatting (from frontend directory)
+- Run `gofmt -w .` for backend formatting
 
 ### Pull Request
 

README.md

@@ -119,6 +119,7 @@ Alternatively, you can run each service separately:
 
 - **Backend**: See [backend/README.md](backend/README.md)
 - **Frontend**: See [frontend/README.md](frontend/README.md)
+- **Full Stack**: Use `docker-compose up`
 - **Sync Server**: Use `docker-compose up syncserver`
 
 ## Testing with Postman

development/README.md

@@ -6,6 +6,9 @@ The `setup.sh` script starts all three services (backend, frontend, and sync ser
 
 > **Note:** The backend should ideally be run in a separate user environment (preferably root user) to avoid permission issues with Taskwarrior configuration files.
 
+
+> **Git Hooks:** Pre-commit hooks are automatically configured when you run `npm install` in the frontend directory. These hooks will format your code before each commit.
+
 ## Prerequisites
 
 Before running the setup script, ensure you have the following installed:

frontend/package-lock.json

@@ -403,7 +403,10 @@
     "dev": "vite",
     "build": "tsc && vite build",
     "test": "jest",
-    "coverage": "jest --coverage"
+    "coverage": "jest --coverage",
+    "postinstall": "git config core.hooksPath .githooks",
+    "lint": "npx prettier --write .",
+    "pre-commit": "npm run lint"
   },
   "keywords": [],
   "author": "",