3 ms·
I use it as part of my daily flow. One example: I work on a feature, which necessitates some refactoring, maybe upgrading a dependency, and oh, while I'm in th
by Legogris 6y ago
I use it as part of my daily flow.
One example: I work on a feature, which necessitates some refactoring, maybe upgrading a dependency, and oh, while I'm in the middle of it I notice some other, unrelated things, that need changing. In order to not have to break my flow and think too much about which changes are required for what, I just commit it all on the same local branch.
This then gets broken up into different branches in individual PRs.
- stevebmark 6y agoI don't understand what this has to do with a visual view of branches and merges
- Legogris 6y agoIt certainly helps me when splitting, comparing and picking changes between branches. Also to keep track of how upstreams have changed compared to my working branch before doing rebases. Oh, and re Githubs fork view (which could be improved on the UI side), is helpful when seeing if anyone else has picked up the ball on unmaintained repos. If you don't find it useful, fine, I don't think we all need to grok each others personal workflows and motivate them to each other? Maybe you can compare it to a visual file manager that visualizes your directory structure as a tree; some people find it a necessity to get an overview of their file system, some don't.