Feature Request: Auto-cherry-pick changes to file origin branches

[hpietukhin]

I'm not sure if this aligns with your roadmap, but here's my use case:
When working with stacked branches, I often modify files that were introduced in earlier branches. I want these changes to appear in the branch where the file was first added, not the current branch.
Right now, I manually cherry-pick these commits back to the appropriate branches and restack. This gets tedious.

Requested feature: Automatically detect commits that modify files and group them by "file origin branch" - the branch where each file was first introduced. Then offer to move these commits to their origin branches.

Alternative: Documentation on extending git-spice for custom workflows like this.
Of course I can modify some fork of git-spice in any case.
Is this something others would find useful?

[abhinav]

Hey @hpietukhin, thanks for the issue.
This is totally something I plan for git-spice to support.
Really, I had two commands I was imagining:

• gs commit sink (gs commit float, sink: Send a commit up or down the stack #560) for when you've already committed the changes and want to send them down
• gs commit absorb to do git absorb down the stack (which does hunk-level grouping instead of just file-level grouping, so even more granular) and restack as needed

Obviously, I can't commit to when this will be implemented, but this is totally something that I expect to exist in the tool.

[hpietukhin]

I would like to offer my help on this. Would you be open to a PR?

[abhinav]

Absolutely! I would try to work with you to make sure that the resulting code and commands fit with existing style and structure, but PRs are definitely welcome.