From Git book, chapter about aliases:
> This technique can also be very useful in creating commands that you think should exist.
I would expect, that when you encounter usability issue fixable that easy, you open an issue and get it fixed. But apparently that's not the case when your software was designed by an engineer
On the other news, I finally added alias for ff, which is just merge --ff-only
Still don't get why of all three ff doesn't have it's own subcommand
@mo oh, i think cargo uses the same idea
you can make an executable titled cargo-xxx, and it will be called if there's no built-in command cargo xxx
@rnd no, it's not about external binaries. It's about aliases for built-in commands, managed in config
git config --global alias.ff 'merge --ff-only'