---
description: Commit on feature branches after work; push means merge to master
alwaysApply: true
---

# Git: commit as you go, push only when asked

## After finishing a change set

- Create or reuse a **feature branch** (do not leave finished work only on dirty `master`).
- **Commit immediately** without asking for confirmation — prefer several small, focused commits over one dump.
- Do **not** push unless the user asks.

## When the user asks to push

“Push” / “naar origin” means this sequence:

0. Run the **full** test suite: `npm test`. **Every test must pass.** Do not merge or push with failing tests — fix failures first (update outdated tests or remove obsolete one-offs; keep generic system coverage).
1. Merge the feature branch into `master` (never fast-forward).
2. Push `master` to `origin`.
3. Delete the local (and remote, if it existed) feature branch — it is obsolete after merge.

Do not leave the finished work only on a remote feature branch unless the user explicitly wants a PR instead of merging to master.
