stg new --fixup <patch>

[koct9i]

Sometimes could be useful to spill changes into temporary patch rather than using stg refresh -p <patch> right away.

[jpgrayson]

It's not immediately clear what the semantics of stg new --fixup <patch> would be and how they would differ from, for example, stg new --refresh <patch>.

[koct9i]

I mean same scenario as git commit --fixup <commit>:
https://git-scm.com/docs/git-commit/2.32.0#Documentation/git-commit.txt---fixupamendrewordcommit

Which add commit with title fixup! <commit-subject>. Such commit could be automatically squashed into original commit by git rebase, or thrown away with ease.

stg new --fixup <patch> will get benefits from shell completion to eliminate thinking about meaningful commit message for tracking connections between commits.

[jpgrayson]

Thanks for the additional detail. The idea makes more sense to me now.

I guess it's the potential to autocomplete patch names that adds the most value here. Other wise stg new -rm 'amend! <patch-name>' gets most of the way there.

Except for this to work with git rebase, the generated message needs to have the patch's commit hash, not the patch name, right? What happens when the target patch is moved in the stack and thus its commit id changes? Seems like the fixup patch would lose its association.

Realistically, I am not going to implement this feature due to lack of bandwidth. I'd consider a PR, but it would be a good idea to elaborate further on the semantics and use cases before getting too deep into an implementation.