4 ms·
To be blunt, if this is a problem you're using git incorrectly. Why would you commit code for fixA on featureB? If you're having issues with commits like this
by brad0 9y ago
To be blunt, if this is a problem you're using git incorrectly.
Why would you commit code for fixA on featureB?
If you're having issues with commits like this you have a people problem, not a fit problem.
- omrispector 9y agoActually, that is exactly the point - Git can be used in ways that obscure history. That is why correct and uniform use are important in a project. As for your question -look at the graph again. fixA was NOT necessarily committed on featureB. Very likely it was not. But it looks that way, due to the way Git manages branches.