Merge first, ask questions later.

GCE e2e build/test passed for commit e26fb81.

• Build Log
• Test Artifacts
• Internal Jenkins Results

@smarterclayton fyi because this fixes something about your original change.

I'm not sure why the munger on your system didn't include this and also why the testing didn't start detecting it until just now. I think the latter was somehow triggered by the release @david-mcmahon just did.

@lavalamp I'd be surprised if it was the update to the branch that caused the master munger to start failing.

I think there's a git command that looks for release branches that maybe suddenly started working?

Yes one of the -munge- scripts actually hardcodes looking for upstream/branch, but prior to today's push the branch already existed so that wouldn't have been 'new'.

Exactly-- that's why I don't understand why it would have stopped working
just now.

On Tue, Jun 21, 2016 at 2:48 PM, David McMahon notifications@github.com
wrote:

Yes one of the munge scripts actually hardcodes looking for upstream/,
but prior to today's push the already existed so that wouldn't have been
'new'.

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#27797 (comment),
or mute the thread
https://github.com/notifications/unsubscribe/AAnglrgKYzhjyIBOtDqEJOmh12-mjQFpks5qOFwxgaJpZM4I7Isl
.