probot | PR Robot is an automated pending pull requests | Runtime Evironment library

The logs did not appear because I did not rebuild my app.
Once I've ran yarn build logs started showing up...

Just to close the question and get an answer.

a really helpful comment from @worthy Alpaca (all credit to them) you can just create a new file, that you can name however you want, according to the schema you already have. Inside that file you can then handle whatever parameters you wish to use with that command

Beside adding a .gitignore, as commented, to incite any contributor to not add a folder, you might consider writing your own GitHub Action in order to reject automatically a PR if the wrong folder is detected.

You can use a GitHub Action like ArangoGutierrez/GoLinty-Action and adapt it in order to check for a folder in the checked out code.
If the test fails, you can then reject the PR.

The example code was not quite clear what the key actually is and where you get it. You need the "repository public key" that you get from the /repos/{owner}/{repo}/actions/secrets/public-key endpoint.

Use the repository public key together with the value from your new secret:

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:

I don't think you can use workflow_dispatch to add/update checks on a PR. This seems to be confirmed by this response to a similar question on the community forums.

Checks are only added/updated for the following events:

• pull_request
• pull_request_review
• pull_request_review_comment
• pull_request_target
• push

So your manual operation needs to trigger one of these events to run. There are probably a number of different ways you can do this, depending on your use case. Just as an example, you could call the API to add a label and allow a pull_request workflow to execute on that type.

After long research I figured it out myself. Posting my solution in case anyone is dealing with the same problem.

1. Setting the passenger log level. You can put passenger_log_level 7 in your nginx configuration /etc/nginx/conf.d/phusion-passenger.conf (for Plesk)
   
   

2. I started the app as a standalone passenger server and got the actual application stdout output. Example: cd in your node app root-folder and run passenger start --startup-file lib/startup.js --nodejs /opt/plesk/node/12/bin/node --log-level 3 --app-type node.

At this point I saw the module Probot couldn't be found in my above mentioned startup script. So I dug a little deeper how a probot app is actually started and stumbled upon the probot run command. By default a probot app isn't run with node ./lib/index.js but probot run ./lib/index.js.

1. Using a custom passenger app start command. I added the nginx option passenger_app_start_command "/opt/plesk/node/12/bin/npm start"; to set the custom start command to use the probot run command defined in the package.json start script instead of the default node ./lib/startup.js from passenger

I learned a lot about these tools and hope this will save someones weekend :D

Would it be possible you need to pass the owner and the repository to context.github.checks.create() method? I think they are required properties: https://octokit.github.io/rest.js/v17#checks

Also, make sure the Github App has the following permissions: checks:write(https://developer.github.com/v3/activity/events/types/#checkrunevent)

Also, checking your code snippet, seems that you are not using the mediaType properly. If you check the type definition, mediaType has the following structure: