summaryrefslogtreecommitdiff
path: root/t/t4254-am-corrupt.sh
diff options
context:
space:
mode:
authorLibravatar Junio C Hamano <gitster@pobox.com>2020-07-29 15:50:01 -0700
committerLibravatar Junio C Hamano <gitster@pobox.com>2020-07-30 12:43:10 -0700
commit6e6029a82acdb3d785eef15dc798f4d86c4ea445 (patch)
treeddca4033ffaca8df143cb20e918d045b15228587 /t/t4254-am-corrupt.sh
parentRevert "fmt-merge-msg: stop treating `master` specially" (diff)
downloadtgif-6e6029a82acdb3d785eef15dc798f4d86c4ea445.tar.xz
fmt-merge-msg: allow merge destination to be omitted again
In Git 2.28, we stopped special casing 'master' when producing the default merge message by just removing the code to squelch "into 'master'" at the end of the message. Introduce multi-valued merge.suppressDest configuration variable that gives a set of globs to match against the name of the branch into which the merge is being made, to let users specify for which branch fmt-merge-msg's output should be shortened. When it is not set, 'master' is used as the sole value of the variable by default. The above move mostly reverts the pre-2.28 default in repositories that have no relevant configuration. Add a few tests to protect the behaviour with the new configuration variable from future regression. Helped-by: Linus Torvalds <torvalds@linux-foundation.org> Helped-by: Jeff King <peff@peff.net> Signed-off-by: Junio C Hamano <gitster@pobox.com>
Diffstat (limited to 't/t4254-am-corrupt.sh')
0 files changed, 0 insertions, 0 deletions