CommitTicketUpdater - git and replayed commits
|Reported by:||pferreir||Owned by:|
I do all my development over two branches, a stable one and an experimental one, which I merge periodically. So, each time I merge
experimental, commits from
stable are again passed on to the ticket updater. So, sometimes this ends up producing duplicate comments and the ticket being closed twice…
My opinion is that could be an option that would somehow trigger the detection of duplicate commits and ignore them. I'm not very sure how to do this, if I should check if there's already a comment with the given commit sha1 associated with the ticket (kind of hacky), or checking the past repository history (ignoring the last changeset) for the commit (not sure how fast it will be).
I would be willing to produce a patch for that, if you believe this is something worth investing time on. Otherwise, I can just try changing a bit my commit hook. However, I believe that this will be a problem with most distributed VCs, so…