Until now, commits where analyzed with `rev-list` default, that is the reverse chronological order. With the introduction of smart commits, it makes more sense to analyze in the chronological order so the first commit that reference "closes something" will actually trigger the close, instead of the last one. The issue can be seen when git commit message summary includes the closing keyword and that the fix is merged with a merge commit. In this situation, the merge commit also embed as part of commit body the summary of the commit it merges. With reverse chronological order, it's the merge commit the will be analyzed first hence close the ticket. By analyzing in chronological order, it's the actual commit of fix that will be seen first. Part of: request #27896 Smart commit is not smart enough Change-Id: I8c1724f4065abe9c636845a54431d5bed6ccbf00

+23 −10

Author

Manuel Vacelet (vaceletm) 2022-07-27 17:19

Committer

Manuel Vacelet (vaceletm) 2022-07-28 17:04

Hash 1eeb4be5d0aaeddf2e01dc2daff6f07f850d35b8

Parent 901b4cf7a59ebeaffe44768176f8e2a250eec46f

Reference git #tuleap/stable/1eeb4be5d0aaeddf2e01dc2daff6f07f850d35b8