What are Some Fundamental Events in a Github Pull Request?

This topic was automatically generated from Slack. You can find the original thread here.

I would expect to see “A pull request was approved”, “A pull request has requested changes”, “A pull request has received a new comment” in here. Those are pretty fundamental events on a Github PR.

Agreed! Could you do us a favor and report this issue in our public repo?

  1. Head over to Support - Pipedream
  2. Click on the “Request an Integration” card.
  3. Select “B - Request changes to an existing integration.”
  4. Fill out the form with details of the issue.
    This way, it gets logged in our public repo, and the component development team can be notified!

Done!

Thanks, I moved the issue to the prioritized column!

Great!

: Pro tip: for maximum security, you can trigger your workflow from whatever GitHub events you want using an HTTP trigger in a GitHub action.

Here’s an example that triggers a workflow on push/merge to master:

The big benefit here is passing the GITHUB_TOKEN to Pipedream:
• This token is temporary, hence much more secure than an long-lived access token.
• It also gives you all the privileges of a full-fledge GitHub App (which you can’t get with tokens or OAuth).

And then the workflow just waits for a response from Pipedream (using a “return HTTP response” step at the end of the workflow).

Thanks! I’ll have a look at that. I think the only downside is setting this up and maintaining it across the many disparate repos i’m involved with

I’ve never made a Github Workflow plugin, but this feels like a candidate for that, for sure.