4 ms·
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
by setheron 6y ago
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?....
- azeirah 6y agoIf 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)
- machiaweliczny 6y agoI just press D in gitup for unrelated changes and continue to spam with commits that are related to feature, works well.
- bellyfullofbac 6y agoWell, as the author said, it's an initial idea. 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...]".
- rorytbyrne 6y agoFunny you say that, because I built that as well: https://github.com/synek/codeline https://github.com/synek/codeline It's even earlier in development than git-plan, but the `commit -m "some message"` command works.