3 ms·
If the second parameter isn't supposed to be there I'd just make another PR removing it. If we use commit ancestry to determine logical dependence then this "r
by recursive 2y ago
If the second parameter isn't supposed to be there I'd just make another PR removing it.
If we use commit ancestry to determine logical dependence then this "revert the bug commit" thing won't work unless the bug just so happens to be in the very last commit.
- brigandish 2y agoYou've created a straw man. No one can make code magically not depend on other code if it does - it's a tautology. No one can argue for better organisation if it's not wanted - feel free to not use a ticket system, don't communicate work, don't rebase work that is interconnected, and don't use logical, atomic commits. I'm not sure that Git is going to be a help given those requirements. As I've already pointed out, I'm not sure what you're arguing against but it's none of the points made in this thread.