Abort a merge or rebase

I started a rebase to tidy commits and now want to abort it — return my branch to exactly how it was before I began the rebase, discard any in-progress conflict resolutions, and leave my working tree unchanged if possible. Abort the rebase and confirm the branch pointer matches the pre-rebase commit and that no temporary rebase state remains.

Before I abort, surface what aborting will discard and what it will keep. Show which commits from the in-progress rebase are already applied, which conflict resolutions are staged but not committed, and whether aborting will lose any local edits I care about. If abort would lose work, recommend a minimal safe stash or patch sequence instead.

I started rebasing feature/cleanup onto develop, encountered conflicts, and have resolved some hunks but not finished. I can't finish this rebase right now and worry that aborting will discard my partially resolved conflict fixes. I don't know whether those fixes are saved in the index or only in working files. What's the safest next step to preserve my work and return to a clean branch state?

Team members often begin interactive rebases to tidy history, then abort halfway and re-run later, creating duplicate work and confusion. Where is training or workflow slipping, and what single rule or checklist would reduce aborted rebases and preserve developer time?