2 ms·
Unless all your features actually fit in one small commit, this doesn't work. Much more common is that you merge a chain of dependent commits, which means you c
by patrick451 2y ago
Unless all your features actually fit in one small commit, this doesn't work. Much more common is that you merge a chain of dependent commits, which means you cannot just rollback a single commit, since that will leave your codebase hopelessly broken. Much cleaner to commit the entire feature as one large commit.
- keybored 2y agoYou can rollback a merge if that is the goal of this one-large-commit.
- keybored 2y agoMore precisely: you can revert a merge.
- necovek 2y agoIf your "features" don't fit in one small commit, you should probably look to redefine what "features" are or at least not tie them to a commit. You can and should split your features into a series of product/codebase improvements that end up delivering the full "feature" with the last of your commits. If done smartly, along the way, you'll be delivering parts of the feature so your users would start benefiting sooner.