Essential session storage is required to sign in. Optional analytics remain off unless you allow them.
Take a small project, initialize a Git repo, and build a clean history: a sensible .gitignore (no build artifacts or secrets), small atomic commits with clear messages, and at least one feature branch merged back into main. Show that you can inspect history (git log --graph), stage selectively, and recover an uncommitted edit you discarded. No giant 'misc changes' commits.
Small, atomic commits with clear, imperative messages; no dump commits; nothing build-/secret-related committed (.gitignore correct).
At least one feature branch created, worked on, and merged into main; history is readable.
Demonstrates selective staging (git add -p or per-file) rather than always git add -A.
Can read history (log --graph/--oneline) and explain what each branch/merge represents.
Use this README structure to make the work reviewable.
DevPath fetches a read-only, size-capped snapshot. Submitted code is never executed.
# Version a project with a clean, deliberate history ## Goal Take a small project, initialize a Git repo, and build a clean history: a sensible .gitignore (no build artifacts or secrets), small atomic commits with clear messages, and at least one feature branch merged back into main. Show that you can inspect history (git log --graph), stage selectively, and recover an uncommitted edit you discarded. No giant 'misc changes' commits. ## Acceptance criteria - [ ] Commit hygiene: Small, atomic commits with clear, imperative messages; no dump commits; nothing build-/secret-related committed (.gitignore correct). - [ ] Branching: At least one feature branch created, worked on, and merged into main; history is readable. - [ ] Staging control: Demonstrates selective staging (git add -p or per-file) rather than always git add -A. - [ ] Inspection: Can read history (log --graph/--oneline) and explain what each branch/merge represents. ## Verification - [ ] Document installation and run commands. - [ ] Record automated checks and their exact commands. - [ ] Add representative output, screenshots, or a short demo where useful. - [ ] Confirm failure paths and known constraints. ## Decision log ### Decision title - Context: - Choice: - Alternatives considered: - Tradeoffs: ## Evidence - Link each rubric criterion to the file, test, or artifact that demonstrates it. ## Known limitations - List what is intentionally out of scope and what should be improved next.