4 ms·

If you're writing a local stack of commits, you need to do an interactive rebase to edit the commits in the middle. You can't just check out and amend earlier c

If you're writing a local stack of commits, you need to do an interactive rebase to edit the commits in the middle. You can't just check out and amend earlier commits in the stack, since git has a branch-first rather than commit-first model (one of its biggest UI failures).

omnipath 4y ago
No, I don't. Again, this seems to be a personal design/preference rather than a behavior git is forcing upon you, which is my point (This isn't a git issue, this is a development workflow that seems needlessly over complicated). When I do development locally, I only commit changes I want to keep. If there is something wrong, or code that needs to be modified, I make those changes, and then commit. When the work is done, if pressed upon me by the team, I rebase the local commits to a single commit before submitting a merge request.
- howinteresting 4y ago
  It's the same development workflow used by the Linux kernel? You know? The project that Git was invented for?
  - bronson 4y ago
    There are tons of different workflows used by Linux Kernel maintainers. Some of them don’t even use Git except to submit patches. Whose workflow are you trying to emulate? (followup question: and why?)
  - omnipath 4y ago
    Are you working on something as complex as the Linux kernel?