"File changes cannot be moved because part of this file was already committed into this branch"

[mtaran]

I thought the whole point of GitButler was to allow moving file/hunk changes between virtual branches? Why does committing some change in file X force all future changes to file X to be "stuck" to that branch? That makes it no more useful than the ability to have multiple changelists open in a single perforce client (which is nice of course, but if you use the feature heavily you inevitably get into unfortunate situations where you want one part of a change to file X to be in CL 1 and another to be in CL 2, which perforce doesn't allow)