[anish-sujanani]

Add a root .gitignore

Addresses PM_GH_REPO_005 — All repositories must define a .gitignore file.

This repository has no .gitignore at its root. One new file, 32 lines, nothing else.

What was chosen and why

The language signal for this repository resolves to the generic minimal template.

Verification

• Exactly one file in the diff, at the repository root; no nested .gitignore touched.
• Every already-tracked file was checked against the new rules with
  git check-ignore --no-index — no tracked file matches any of them.
• .env.* precedes !.env.example deliberately: git applies the last matching pattern, so
  reversing them would ignore a committed example file too.

Break risk

None at runtime. Adding a .gitignore changes nothing about existing tracked files and
nothing about CI.

[nitpickybot]

AI Review Summary

Adds a minimal root .gitignore covering OS/editor noise, logs, and .env variants. The pattern ordering for .env.example is correct (last match wins). Nothing blocking; one minor note on .vscode/ if the repo ever wants to share editor config.

• 🔵 1 suggestion(s)

Review Scope

• Mode: Full pull request
• Range: Full pull request through ca34ee45e94d2296c97c21861c8ff0f3ed506b08
• Current range coverage: Complete
• Cumulative pull request coverage: Complete

---

This review is complete for the current scope. Addressing all critical and warning findings above satisfies the review; suggestions are optional. Request another review only if subsequent changes introduce new behavior or materially expand the pull request's scope.

[nitpickybot]

🔵 suggestion

Ignoring all of .vscode/ means shared settings like extensions.json, launch.json, or settings.json can never be committed. If you want to leave that door open, the usual pattern is to negate the shareable files:

Suggested change

	.vscode/
	.vscode/*
	!.vscode/settings.json
	!.vscode/tasks.json
	!.vscode/launch.json
	!.vscode/extensions.json

Entirely optional — fine to keep as-is if the repo has no shared editor config.