t1300: demonstrate that CamelCased aliases regressed
It is totally legitimate to add CamelCased aliases, but due to the way config keys are compared, the case does not matter. Except that now it does: the alias name is expected to be all lower-case. This is a regression introduced by a9bcf6586d1 (alias: use the early config machinery to expand aliases, 2017-06-14). Noticed by Alejandro Pauly, diagnosed by Kevin Willford. Signed-off-by: Johannes Schindelin <johannes.schindelin@gmx.de> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Johannes Schindelin committed
Jul 14, 2017 at 10:39 UTC
084b04409312e8d95aa51edb04dde7ff56f66fba
1 file changed
+7
t/t1300-repo-config.sh
+7
@@ -1075,6 +1075,13 @@ test_expect_success 'git -c works with aliases of builtins' '
1075
test_cmp expect actual
1076
'
1077
1078
+test_expect_failure 'aliases can be CamelCased' '
1079
+ test_config alias.CamelCased "rev-parse HEAD" &&
1080
+ git CamelCased >out &&
1081
+ git rev-parse HEAD >expect &&
1082
+ test_cmp expect out
1083
+'
1084
+
1085
test_expect_success 'git -c does not split values on equals' '
1086
echo "value with = in it" >expect &&
1087
git -c core.foo="value with = in it" config core.foo >actual &&