Skip to content

Conversation

@abhinav
Copy link
Owner

@abhinav abhinav commented Sep 20, 2025

If there are unstaged changes in the worktree when using commit fixup
to fix up a downstack branch, we should not pop the autostashed changes
until after the upstack restack is complete,
and we've switched back to the original branch (not the fixed branch).

Ref: #867 (comment)

[skip changelog]: New entry not required as fixup hasn't been released yet.

@abhinav
Copy link
Owner Author

abhinav commented Sep 20, 2025

This change is part of the following stack:

Change managed by git-spice.

If there are unstaged changes in the worktree when using commit fixup
to fix up a downstack branch, we should not pop the autostashed changes
until after the upstack restack is complete,
and we've switched back to the original branch (not the fixed branch).

Ref: #867 (comment)
@abhinav abhinav force-pushed the commit-fixup-autostash branch from 9106a77 to c757acd Compare September 20, 2025 18:06
@abhinav abhinav merged commit 5938483 into main Sep 20, 2025
22 checks passed
@abhinav abhinav deleted the commit-fixup-autostash branch September 20, 2025 18:15
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants