probot.github.io | This is the home of probot documentation apps | Static Site Generator library

You'll need to pull the PR changes locally and for you to sign them off.

The purpose of the sign-off is to indicate you've looked at these changes, not just to verify the identity of the author. You can still sign off the commits made by Snyk.

But GitHub won't do that in its PR on your behalf.

This was my mistake.

This is the whole probot.event.js file:

You must start the app programmatically. This way you can access the Express app AFTER probot loads but BEFORE Probot starts running:

What is the purpose of the pull_request event , if its other specific forms (like pull_request.reopened) carry no different information(more precisely, if their contexts contain no different infos) ?

This is just a feature of Probot to simplify processing webhook events from GitHub. I'll try and explain why it's helpful.

If you were to consume webhook events without Probot, you would have to parse every pull_request event, check the action field for a case, and decide whether to handle it.

There are several events that have a top-level action field in the payload, incuding:

• check_run
• issue
• project
• pull_request
• and many more in the docs...

Rather than make application developers perform this parsing and inspection of the JSON themselves they decided to simplify the callbacks so you can subscribe to webhooks using the specific [event].[action] pattern, and the framework takes care of invoking your callback when the matching event and action is received.

So you have two options for handling pull_request events:

• if you don't know which events you need, or need to dynamically process events, subscribing to pull_request is how you would receive all pull request events
• if you know which events you should handle, and can ignore the rest, subscribe to explicit pull_request.[event] should simplify your application code

You could also subscribe to *, which represents all events the probot app receives, rather than explicitly listing all supported events in your app.

If you use Probot, you don't need to load your own @octokit/rest or any of the @octokit/auth-* packages, it's all built into Probot

Did you try the example code shown on https://probot.github.io/