www-infrastructure-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Sam Ruby (JIRA)" <j...@apache.org>
Subject [jira] [Moved] (INFRA-11379) Duplicate emails after git merge
Date Sat, 05 Mar 2016 12:48:40 GMT

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

Sam Ruby moved WHIMSY-52 to INFRA-11379:
----------------------------------------

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

> Duplicate emails after git merge
> --------------------------------
>
>                 Key: INFRA-11379
>                 URL: https://issues.apache.org/jira/browse/INFRA-11379
>             Project: Infrastructure
>          Issue Type: Bug
>          Components: Git
>            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)

Mime
View raw message