title: How do I make Jenkins see a Git merge commit as a change?
body: <p>Users A and B each make modifications (on different feature branches) to a particular repo.</p>
  
  <p>User A merges changes into staging branch.  Jenkins builds the staging branch, and succeeds.</p>
  
  <p>User C (release manager for User B team) merges User B’s changes into staging branch.  However, something in the merge goes wrong and isn’t noticed, such as a conflict that wasn’t resolved properly.</p>
  
  <p>Jenkins builds the staging branch, and fails because of the bad merge.</p>
  
  <p>Users A and B are notified of the build failure, because their code was part of the merge, even though their changes were not at fault.  User C never gets a failure notice, even though his bad merge was what broke the build.</p>
  
  <p>Is there a way to:</p>
  
  <ol>
  <li>Cause Jenkins to treat merge commits as changes?  (There is the very real possibility that code will actually be modified during a merge!)</li>
  <li>Notify User C (as the merge committer) along with users A and B?</li>
  </ol>
  
  <p>We are using the <a href="http://wiki.jenkins-ci.org/display/JENKINS/Git+Plugin" rel="noreferrer">Git</a> and <a href="http://wiki.jenkins-ci.org/display/JENKINS/Email-ext+plugin" rel="noreferrer">Email-ext</a> plugins for Jenkins.</p>
  
  <p><strong>Edit, several months later:</strong> Still having issues with this — even in a scenario where the person who did the merge did not introduce breaking changes, it would still be nice for them to be notified that the build succeeded (or failed).</p>