You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Daniel Gruno (JIRA)" <ji...@apache.org> on 2016/03/06 06:04:41 UTC

[jira] [Assigned] (INFRA-11379) Duplicate emails after git merge

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

Daniel Gruno reassigned INFRA-11379:
------------------------------------

    Assignee: Daniel Gruno

> Duplicate emails after git merge
> --------------------------------
>
>                 Key: INFRA-11379
>                 URL: https://issues.apache.org/jira/browse/INFRA-11379
>             Project: Infrastructure
>          Issue Type: Planned Work
>          Components: Git
>            Reporter: Sam Ruby
>            Assignee: Daniel Gruno
>            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)