Robert Dailey <rcdailey.lists@xxxxxxxxx> writes: > Is there a config option or some way for `git tag -a` to be the > default? I could create an alias but would make more sense to have a > config: > > git config --global tag.alwaysannotate true If you really wanted to, you could do the following (and you must to do all of the following): * Introduce "git tag --no-annotate" option, that defeats the effect of such a configuration variable. * Devise some way to reliably catch scripts that use "git tag" without saying what kind of tag they want to create. Add new code to issue a warning message saying that the script will be horribly broken when user starts using the configuration variable that will be introduced in the future. This will force them to be updated to pass the "--no-annotate" option. * Wait for several releases to make sure that no script that want to use light-weight tags use "git tag" without "--no-annotate" option. * Introduce the configuration variable. I personally do not think it is worth it, and also I do not know what that "some way to reliably catch" would look like. We gave short-and-sweet "-a" and "-s" options exactly because we wanted to make it easy to type them. Also, "tag -m msg" will DWIM to "-a". -- To unsubscribe from this list: send the line "unsubscribe git" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html