3 ms·
> At my last job we did exactly that (no squash though), then our branch got merged to the development branch and the commit messages would be all stacked on to
by scarface_74 3y ago
> At my last job we did exactly that (no squash though), then our branch got merged to the development branch and the commit messages would be all stacked on top of each other. But we had a policy to include the jira ticket in all commit messages so the commit messages were still useful.
This is against every best practice since I started using git over a decade ago.
> You don't need guarantees of atomicity
Am I really having this argument in 2023 that you should be using a code syncing process that guarantees atomicity?