kramme:fixup-changes

To automate fixup commits for unstaged changes, this workflow maps each modified file to its most recent commit, creates fixup commits, and applies an autosquash rebase to maintain a clean history.

The best way to squash unstaged changes into existing commits is mapping files to their target commits, creating fixup commits, and running an autosquash rebase after validating build, tests, and lint checks.

When creating fixup commits, orphan files not tied to existing commits trigger user prompts to decide how to handle them, ensuring new or unrelated files are properly integrated or excluded from the workflow.

Yes, you can skip tests and lint validation during an autosquash rebase by passing the --skip-tests flag, which bypasses validation checks before squashing fixup commits into target commits.

Yes, this git workflow supports specifying a custom base branch for rebasing by passing the --base flag, allowing you to target a specific branch rather than the default when applying the autosquash rebase.

To run fixup commits without confirmation prompts, pass the --no-confirm flag to skip interactive prompts during the workflow, which automates orphan handling and user decisions for a streamlined process.