I agree this happens quite often. Since Highflux automatically commits changes to the current branch it is extremely easy to switch to a different branch with j

I agree this happens quite often. Since Highflux automatically commits changes to the current branch it is extremely easy to switch to a different branch with just one click (or CLI command). (so no stashing / dealing with untracked files is needed) Then you can implement the side change separately and then switch back again to your first feature branch. Those two feature branches are then unrelated, we are planning to add stacked changes in a future version.