Ævar Arnfjörð Bjarmason <avarab@xxxxxxxxx> writes: > On Tue, Jul 04 2017, Łukasz Gryglicki jotted: > >> add --signoff flag to `git-merge` command. > > We'd usually say this as: > > merge: add a --signoff flag > > Or something like that. I thought I gave a fairly complete example that can be imitated, but apparently it didn't go through X-<. >> Some projects require every commit to be signed off. >> Our workflow is to create feature branches and require every commit to >> be signed off. When feature is finally approved we need to merge it into >> master. Merge itself is usually trivial and is done by >> `git merge origin/master`. Unfortunatelly this command have no --signoff >> flag, so we need to either add signoff line manually or use >> `git commit --amend -s` after the merge. First solution is not ideal >> because not all developers are familiar with exact sign-off syntax. >> The second solution works, but is obviously tedious. >> This patch adds --signoff support to git-merge command. It works just >> like --signoff in `git-commit` command. > > It would be nice to split this into a at least a couple of paragraphs, > and more closely follow the format suggested by > Documentation/SubmittingPatches. Good suggestion. >> More details here: >> https://public-inbox.org/git/CAHv71zK5SqbwrBFX=a8-DY9H3KT4FEyMgv__p2gZzNr0WUAPUw@xxxxxxxxxxxxxx/T/#u > > These more details include my outstanding question in > 87fueferd4.fsf@xxxxxxxxx which hasn't been answered yet. I have an opinion on that topic, but I'd prefer to hear from others first before I speak out. >> diff --git a/t/t9904-git-merge-signoff.sh b/t/t9904-git-merge-signoff.sh >> new file mode 100755 >> index 0000000000000..f542f136f5dda >> --- /dev/null >> +++ b/t/t9904-git-merge-signoff.sh > > The convention for adding new tests is not to add a new one after > whatever name sorts the highest, see "Naming Tests" in t/README. Correct. > I.e. this should be somewhere in t[6-7]* with the other merge tests. Yeah. While most of t[67]??? series are about the contents of the merge, i.e. resulting trees and what happens in the working tree, there are some tests about the merge messages in there. t7608 is exactly about how the command prepares the messages before giving them to human to edit, and I think "merge can be told to optionally add sign-off" fits there just fine. All existing tests there are only interested about the title, but that does not mean there must not be tests that care more than the title in the script. Also, as you suggest, these will become a lot shorter when the standard test helper shell functions are used. I do not think we necessarily want a brand new test script to test only three or so combinations (i.e. last one wins when --option and --no-option is given, --option has an effect, --no-option does not have an effect).
