Require pull_request in GitHub payload instead of specific event

[shivghai]

Currently, we require the REPORT_COMMIT command to be triggered on the pull_request command. This is not necessary, since the only blocker here should be for us to have the pull_request payload in the GitHub Event

[shivghai]

• Require pull_request in GitHub payload instead of specific event #25 👈 (View in Graphite)
• main

This stack of pull requests is managed by Graphite. Learn more about stacking.

[zwaxman]

Wait actually do we want to do this? Don't we want them to start reporting on their merges (what I'm working on now). Do they run their pipeline on the pull_request event "merge" action (I think this is less commonly the case), or on a "push" event to main. They're not already running reportCommit on merge, are they? I think we need to double check with Vinko about this

[zwaxman]

Think we need to double check with Vinko how they will trigger their merge pipelines. I think on a "push" event to main is much more common pattern than to run on the pull_request event "merge" action.

[zwaxman]

Or I guess for our sakes, we could just require they run on the pull_request "merge" that's definitely easier for us to implement, I just think that's a less common pattern, so don't know if we'll get pushback from other clients here.