This article talks about doing fixup changes while working on the "plan".
The utility offered though doesn't address the fact that now non-related changes are still bundled together.
We've just managed to write the git commit message earlier?....
The utility offered though doesn't address the fact that now non-related changes are still bundled together.
We've just managed to write the git commit message earlier?....
So you're working on "git plan --commit-message='important feature'" or whatever the syntax would be.
Then you encounter a place where some refactoring would be really helpful, so you do
"git plan --commit-message='refactor: ...'"
Any changes made during this plan won't show up in the original git plan.
I'm not sure if this is how it works, but that's how I understood it.
In reality, git-plan just keeps a directory of draft commit messages for you, and when you run `git plan commit` you can choose one of them to use as the template for your commit message. Essentially, it runs `git commit -t <YOUR_PLAN_FILE>`.
(I'm the author)
I suppose an ideal tool would be for me to highlight a bunch of lines in the IDE, say "These code changes are part of plan: [ABC/XYZ/Create a new plan...]".
It's even earlier in development than git-plan, but the `commit -m "some message"` command works.