Add option to use `git revise` instead of `git rebase`

[alerque]

I would greatly speed up some of my workflows (and reduce issues with live local testing since the working tree would remain untouched during the process) if git absorb could trigger git revise instead of git rebase for its needs. I currently do this manually, but having it automatically triggered like rebase can be would be nice.

The only major difference is rebase needs the --autostash argument, while this does not exist and is not relevant with git revise. Otherwise the usage should be the same.

I would expect something like --and-revise or --and-rebase --use-revise to accomplish this.

[blairconrad]

@alerque, I wasn't familiar with the "revise" subcommand, so quick searched. You're referring to third-party git subcommand git-revise?

[alerque]

Yes, that's it. In many ways for this use case it will work out just like git rebase, but under the hood it operates at a lower level and does not need to replay the actions in the working directory. None of the HEAD files in the file system ever need to change, only the Git tree gets operated on in the background. This makes it much faster, and it doesn't throw other tooling into a tizzy (like editors or file system watchers or anything with files open) because the actual operation happens in the background. This makes it much more practical to continuously send large numbers of git absorb generated fixup commits to where they actually go without messing up the working copy or pausing other work.

[tummychow]

i will accept --and-revise, but nothing beyond that. we're pushing into the territory of "i want git-absorb to be able to run any command any way i like" here.