Philip Waritschlager

The branch colors are currently calculated based on the hash of the branch names. The list of colors from which is chosen is hard coded. There's been an issue somewhere...

implemented with latest release v0.1.20 edit: via icon in the file changes listing. I'm not really sold on adding that as a context menu entry And thanks @SeijiSuenaga for linking...

> Do not allow multiple selections (more than two) with Ctrl+click but it's really handy for cherry-picking and reverting them :/ > Allow selection of multiple commits (without gaps) with...

> No, shift + click doesn't work with v0.1.14 on my machine... are you using MacOS?

> No, shift + click doesn't work with v0.1.14 on my machine... @hansu is this still the case in the latest release? > As an initial iteration, could the squash...

Leaving aside the UI problem above, a non-interactive squash can be achieved using `git reset --soft [commit id of parent of oldest commit to squash] && git commit`. That can...

thanks for the report. this looks a bit difficult to debug as I think this isn't reproducible on just any kind of merge commit. > Instead the branch diverges before...

ah wait, it *does* seem to be erroneous for every kind of ``` |/ * ``` branch birth commit, the line starts one commit too early. This doesn't seem critical...

Should be fixed with v0.1.20 later today, both the wrong birth branch positioning and missing merge commits. Please give it a try. > Preferably, we'd have the line's branching from/to...

hey, sorry for the delay, TBH I have no idea what's causing this. Let me know if you figure it out. I want to change all the dependencies to something...