was hoping that I could get some insight into how you made the choices you did for testing drone’s own PRs, and what your degree of trust is that you’re not testing the wrong commits yourself on incoming PRs.
Keep in mind that this was not an issue until recently, within the past 6 months. GitHub must have made an internal change because for ~4 years this was not a problem, and everything started blowing up one day. It is likely that other CI systems are having similar issues, since we based our clone logic off of Travis, which seemed like a safe bet at the time.
So the current state of merge refs was not really a choice we made voluntarily – GitHub changed and forced us into this situation. This change has not had a material impact on Drone, aside from requiring me to restart a few builds from time to time. Most of our customers switch to head ref, which is why there has not been much urgency on my end.
I’ve been going around in circles about the right thing to do here
We have come up with a proposed solution here: Pipeline Event Merge Requests w/GitLab