Hello ralph wave I have a question regarding triggering provider verification from the OSS pactbroker. For our CI, we use GitHub actions. I am curious about how you handle authorization for triggering GitHub actions from pactbroker. It can be done easily with a dispatch event and setting a JWT token in the header. We set up a webhook in the Pact Broker following way

{
  ....
  "request": {
    "method": "POST",
    "url": "<https://api.github.com/repos/oracle/customer-service/dispatches>",
    "headers": {
      "Authorization": "Bearer GITHUB_TOKEN"
    },
 "body": {
      "event_type": "contract_requiring_verification_published",
....

However, I am interested in where exactly you get that Authorization token. The only option that seems possible is to use some sort of GitHub CI account and generate a token for it that is valid indefinitely. But for several reasons, we don't want to use this option. I would say that normally, this situation would be handled by creating a GitHub application and dynamically generating a token before every request to github, but if I'm not mistaken, pactbroker does not support this. How do you handle this situation?

Unfortunately we require a PAT at this stage, which could either be from an individual user or service / CI account