docs: address review (compose v2 note, rebase tip, commit example); chore: add setup:ci and engines

Author: rushi-018

CONTRIBUTING.md

@@ -55,7 +55,7 @@ github_tracker/
 4. Commit your work to your topic branch and push to your fork:
    ```bash
    git add .
-   git commit -m "feat: add contributor quick-start to README"
+   git commit -m "docs(readme): add contributor quick-start"
    git push -u origin <topic-branch>
    ```
 5. Open a Pull Request from `<your-username>:<topic-branch>` to `GitMetricsLab:main`.
@@ -65,6 +65,8 @@ github_tracker/
    git rebase upstream/main
    # if you've already pushed, use a safe update:
    git push --force-with-lease
+   # Note: use --force-with-lease only on your own topic branch after a rebase.
+   # Avoid force-pushing shared branches.
    ```
 
 ### Commit Conventions
@@ -75,7 +77,7 @@ Use Conventional Commits. Examples:
 - `fix(auth): handle missing session cookie`
 - `feat(tracker): add contributor activity chart`
 
-This helps with change logs and automated releases. See https://www.conventionalcommits.org/.
+This helps with change logs and automated releases. See [Conventional Commits](https://www.conventionalcommits.org/).
 
 ### Sign-offs / DCO (Optional)
 

README.md

@@ -22,6 +22,10 @@ Want to contribute? Here’s how to get started:
   ```bash
   git fetch upstream && git rebase upstream/main
   ```
+  If you already pushed before the rebase:
+  ```bash
+  git push --force-with-lease
+  ```
 4. **Make your changes** (e.g., edit `README.md` to improve instructions).
 5. **Commit and push**:
   ```bash
@@ -92,12 +96,6 @@ Fallback (manual):
 npm install
 cd backend && npm install
 ```
-> Tip: Use the project’s Node.js version. If you’ve set it in `.nvmrc` or `package.json#engines`, nvm will pick it up.
->
-> With nvm:
-> ```bash
-> nvm use
-> ```
 
 ### 2. Configure environment variables (backend)
 Copy the sample env file and set required variables:
@@ -145,6 +143,9 @@ If the backend runs locally, it typically listens on <http://localhost:5000> (or
 
 Alternatively, to start the full stack with Compose:
 
+> Requires Docker Compose v2 (Docker Desktop or standalone Compose v2 CLI).
+> See https://docs.docker.com/compose/ for installation and upgrade instructions.
+
 ```bash
 # Dev profile (hot reload etc.)
 npm run docker:dev
@@ -188,7 +189,6 @@ npx jasmine --config=spec/support/jasmine.mjs
   # Use a test database (e.g., github_tracker_test) to avoid clobbering dev data
   MONGO_URI="mongodb://127.0.0.1:27017/github_tracker_test" npx jasmine --config=spec/support/jasmine.mjs
   # Or cross-platform with one command:
-  # (one-time) npm install --save-dev cross-env  # in the repository root
   npx cross-env MONGO_URI="mongodb://127.0.0.1:27017/github_tracker_test" jasmine --config=spec/support/jasmine.mjs
   ```
 

package.json

@@ -3,12 +3,17 @@
   "private": true,
   "version": "0.0.0",
   "type": "module",
+  "engines": {
+    "node": "18.20.x"
+  },
   "scripts": {
     "dev": "vite --host",
     "build": "vite build",
     "lint": "eslint .",
     "preview": "vite preview",
-  "setup": "npm install && npm --prefix backend install",
+    "setup": "npm install && npm --prefix backend install",
+    "setup:ci": "npm ci && npm --prefix backend ci",
+    "backend:install": "npm --prefix backend install",
     "docker:dev": "docker compose --profile dev up --build",
     "docker:prod": "docker compose --profile prod up -d --build"
   },