You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@whimsical.apache.org by "Chris Lambertus (JIRA)" <ji...@apache.org> on 2016/03/05 07:56:40 UTC

[jira] [Moved] (WHIMSY-52) Duplicate emails after git merge

     [ https://issues.apache.org/jira/browse/WHIMSY-52?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Chris Lambertus moved INFRA-11117 to WHIMSY-52:
-----------------------------------------------

    INFRA-Members:   (was: [infrastructure-team])
      Component/s:     (was: Git)
         Workflow: jira  (was: INFRA Workflow)
              Key: WHIMSY-52  (was: INFRA-11117)
          Project: Whimsy  (was: Infrastructure)

> Duplicate emails after git merge
> --------------------------------
>
>                 Key: WHIMSY-52
>                 URL: https://issues.apache.org/jira/browse/WHIMSY-52
>             Project: Whimsy
>          Issue Type: Bug
>            Reporter: Sam Ruby
>            Priority: Minor
>
> Description of the problem:
> https://mail-archives.apache.org/mod_mbox/whimsical-dev/201601.mbox/%3CCAOGo0VaZw01Xs7+R7dZSjc4o3Td_X4tBSzi1o+Wh92B3=g9OGw@mail.gmail.com%3E
> The root cause appears to be that common git workflows produce new commits by "replaying" deltas in other branches as a part of a merge; these new commits are then considered distinct, and even flagged as such by the PushEvent GitHub webhook:
> https://developer.github.com/v3/activity/events/types/#pushevent
> It might be worth exploring how other software projects deal with this (and/or making use of existing hooks).  One such example:
> https://github.com/git-multimail/git-multimail/blob/master/git-multimail/git_multimail.py#L3077



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)