# Knowledge Check: Engineering Git Workflow

---

**1. Why does bundling unrelated changes into one commit cost you something real, not just
style points?**

*Answer:* It makes precise operations like `git revert` impossible to apply to just ONE logical
change — reverting the commit reverts everything in it together, whether you want that or not.

---

**2. Why do teams typically restrict direct, unreviewed pushes to `main`?**

*Answer:* `main` is the shared source of truth everything else (deployments, other branches) is
built from — protecting it reduces the chance an unreviewed mistake reaches something everyone
else depends on being trustworthy.

---

**3. Name one concrete way this course's Git discipline connects to GitOps or CI/CD.**

*Answer:* Any reasonable answer connecting small deliberate changes / a trusted source of truth
/ review-before-merge / reliable history to how CI/CD pipelines trigger on pushes or how GitOps
treats a Git repository as the authoritative record of desired infrastructure state.

## Instructor Notes

**Facilitation:** Question 3 is open-ended by design — the goal is students making the
connection in their own words, not reciting a fixed answer.

**Approximate timing:** 5 minutes.