Open jamielennox opened 7 years ago
Yea.. I'm not sure how we are actually hitting this in production with our current workflows, but it's not too difficult to reproduce by simply creating two branches from the a single sha and proposing a PR from each.
Perhaps we can finagle a way to post an error comment back to the PR informing the user of the scenario and suggesting they clean things up?
We can possibly handle this Exception by reporting to all found PRs that multiple PRs were found, preventing processing.
This is an unusual situation, but apparently it happens. You can end up with the same sha in the top of multiple pulls and then zuul isn't happy.