Idea: "unapplying"/"hiding" commits

[andrewabbott-invetech]

Sometimes I feel like I want to temporarily "unapply"/"hide" commits in a stack without actually discarding them.

For example, if I have a stack like this:

For example, if a commit is incomplete and causes compile errors, but I don't want to discard it because I will finish it later, and it still logically belongs in the branch. Or if I want to temporarily unapply some number of commits from the tip of the stack, like checking out an earlier commit directly (detached HEAD) in Git. It seems intuitive to me to be able to right click a commit and "unapply it".

I think this can mostly be emulated right now using separate temporary independent branches, though I'm unsure about how dependent changes interact with this. The main advantage of this idea for me is it keeps commits in a stack in the right place while they are unapplied, so I don't have to remember where to move the commit back to.

If there are already workflows people do with GitButler in the same vein, I'd love to hear about it too.

[Byron]

Thanks a lot for sharing, that's a very interesting indeed, and at least right now prohibitively hard to implement.

However, something that I see as a very achievable feature is to be able to 'hide the effects' of commits in a sequence starting from the tip to the stack. Here, you could hide, "Fixes that I like", or that and "Some change that isn't ready yet", and so on.