5 ms·
If I understand the proposal correctly, it works like a stack. So you're working on "git plan --commit-message='important feature'" or whatever the syntax woul
by azeirah 6y ago
If I understand the proposal correctly, it works like a stack.
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.
- rorytbyrne 6y agoThat is not how it works, but it's an interesting idea. My worry is that it's a little fragile in the same way that vanilla git is fragile - you can accidentally start working on a new task and mess up your stack. 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)