Open laraPPr opened 5 months ago
Haven't had time to really look into your issue, but regarding the $GITHUB_TOKEN
: it's being used by PyGHee here https://github.com/boegel/PyGHee/blob/main/pyghee/lib.py#L72.
Haven't had time to really look into your issue, but regarding the
$GITHUB_TOKEN
: it's being used by PyGHee here https://github.com/boegel/PyGHee/blob/main/pyghee/lib.py#L72.
Thanks thats the code i was looking for. I’ll see if this helps me.
I found a solution you can check the changes that I made to the bot here:
At the UGent we are currently looking at letting the bot handle a private repo. The bot could handle the events from created prs, and commando in the private repo without any issues.
However the
bot: build
commando is not able to execute and errors out. This does not crash the event handler but the build job also never gets started. and there is also not anything posted to github that indicates that the ´event_handlerran into a problem when handling the
bot: build` command.When going into the Pyghee logs the error was very clear.
First error I ran into was the following:
This error I resolved by updating the adjusting the clone commando in
tasks/build.py
. This solution requires however that there is a valid private key linked to a GitHub account. Which is the case on my bot machine.After implementing the solution above I ran into a seccond error:
A possible solution is adjusting the
curl
commando to the following:I However do not have a working solution yet. This solution requires the access to $GITHUB_TOKEN variable after the EESSIBotSoftwareLayer flask app is created. which seems to not be possible. I also cannot tell where the $GITHUB_TOKEN variable is used so I don't know if it can be a solution to create an
.env
file for the $GITHUB_TOKEN and $GITHUB_APP_SECRET_TOKEN variables. At the moment however I cannot figure out where these variables are used when creating the app. I only know that when trying to create app without the $GITHUB_TOKEN you get the following error.And I'm struggling to figure out from where this error is coming.