@dimaulupov I asked on the issue, but I think I'd rather see an option here just for --no-commit. Does the --no-ff have any effect with --no-commit?

@eamodio sorry for nor replying earlier.

Main reason why --no-commit is not enough is that it does not work for branches that can be fast-forwarded.

I am reviewing other branches and merging them into main.

Easiest way (for me at least) to review the code and see changes in overall is to use highlighting features for changes in vscode. It is possible to start the code, see what it does, etc. Quite often branches are not ready and I often reset my main branch after looking at the changes.

It means I need to just apply changes from other branch, but not actually commit.
If branch is diverged a lot, --no-commit works great. It just applies everything, stages and stops.
But if branch can be fast-forwarded, --no-commit does nothing. Merge just adds all the other branches commits into my branch. So I can't easily see what changed and also unable to reset (with just one command).
So you need both --no-commit and --no-ff to cover both scenarios.

@dimaulupov Thank you for the extra information -- very helpful!

Thank you so much for your contribution!