Re: git alias for options

From: Ævar Arnfjörð Bjarmason <avarab@gmail.com>
Date: Feb 17, 2017, 13:50 UTC
Message-ID: <CACBZZX4Zmwb8ZHGBXCpm6=yH_uxc-K1X1vv1jQ+wwnUPneqM4A@mail.gmail.com>
In-Reply-To: <CAM_JFCz+9mxp37BTT7XPJ0fMd41DdbAxnvQF7id9msH+SDe6_Q@mail.gmail.com>

On Fri, Feb 17, 2017 at 9:23 AM, hIpPy <hippy2981@gmail.com> wrote:

> Git has aliases for git commands. Is there a (an inbuilt) way to alias
> options? If not, what is the reason?

This has long been on my wishlist, because there's a lot of copy/pasted logic all over Git to make git foo --whatever aliased to foo.whatever in the config, but only for some options.

It should ideally be part of something every option just supports, via the getopts struct.

However, it can't allow you to modify whatever option you want, because some things like git-commit-tree should not be customized based on config, it would break things that rely on the plumbing commands.

So it would have to be a whitelist for each option we allow to be configured like this via the getopts struct.

Also there are surely other edge cases, like maybe the config option now doesn't 1=1 map to the name for the option in some cases, or the flag should be config-able but is has no long form (which we'd like for the config), then we'd want to add that etc.