git said the feature shipped
A commit is halfway: software ships when you watch a customer complete the intended action live.
Git said the feature shipped. The customer’s screen said otherwise. A commit is halfway because shipping ends when a user can actually do the thing.
when is a feature actually shipped?
A feature is shipped when a user is doing the thing it was built for.
Merged code, green CI, and a closed ticket can still leave the customer unable to use it.
why does repo activity feel like progress?
Repo activity produces visible signals: commits, merges, CI, and ticket movement.
Those signals describe work moving through the repository. They do not show whether the customer’s screen works.
what did the customer screen reveal that Git missed?
Git said the feature shipped. The customer’s screen said otherwise.
That gap is the receipt: repository status cannot stand in for watching the feature work live.
what should count as done on a team?
Done should include seeing the intended user action work live.
A commit is halfway. The remaining half is the customer experience.
Does green CI mean a feature is shipped?
Green CI shows that CI is green. It does not show that a customer can complete the intended action on their screen.
Is a merged commit considered done?
A merged commit is halfway. The work reaches done when a user is doing the thing the feature was meant to enable.
Why can a closed ticket still hide a shipping problem?
Tickets can close after repository work is complete. The customer’s screen can still reveal that the feature does not work live.