3 ms·
Hey folks, I'm the author. Context-switching is hard. Having the discipline to prioritise effectively is hard, using git branches effectively is hard, and buil
by rorytbyrne 6y ago
Hey folks, I'm the author.
Context-switching is hard. Having the discipline to prioritise effectively is hard, using git branches effectively is hard, and building tools to magically make it easier is...hard.
Git-plan doesn't solve this problem outright, but I hope it moves in the right direction.
I do think that once you have draft commit messages in your workspace, it is possible to build new tools that consume them to help you context switch. For example, a tool could automatically stage hunks for you, based on the draft commit message you wrote.
There are some great thoughts and criticisms here and I'll be taking them all onboard for the next couple of versions of the tool. If anyone wants to contribute, PRs are welcome and I can help out as needed.
- busterarm 6y agoIf you have a good code review system, like Gerrit or Rietveld, you can do what I do. Every single commit and upload is immediately followed by `git checkout -B master origin/master`. Use WIP tags for things you intend to keep working on and download the patch and upload new patch sets as you continue. Using the code review tool as a substitute for branches and continuously doing work off of a clean master has changed my life.