A developer has local workspace changes that are not committed. Why should the team distinguish them from a shared branch state?

Published
  1. Other collaborators and build jobs may not have those uncommitted changes
  2. Git branches are only cosmetic labels on screenshots
  3. Every keystroke automatically changes the production extension
  4. Uncommitted changes automatically become approved releases

Comments — 0