This website uses cookies to ensure you get the best experience.
Learn more.
A developer has local workspace changes that are not committed. Why should the team distinguish them from a shared branch state?
Published
- Other collaborators and build jobs may not have those uncommitted changes
- Git branches are only cosmetic labels on screenshots
- Every keystroke automatically changes the production extension
- Uncommitted changes automatically become approved releases
Comments — 0
Sign in to comment