In order to leverage kernel-patches-daemon you will need an app on github which has permissions to push pull requests onto a tree which will in turn leverage a self-hosted runner.
You should lock down your repo / organization so to ensure only privileged developers can issue pull requests. In the future perhaps kpd can instead be modified to only work with git pushes, as by default the security for pushes on repos are locked down, whereas anyone can typically issue pull requests on most open source projects.
Uploading a full tree to github takes a long time. To reduce the amount of time it makes sense to just fork Linus own github tree and use that as a base for your organization to then use this tree to fork from. The reason we do this is that kpd issues pull requests onto the original tree. This can also be avoided perhaps in the future if kpd did not issue pull requests and instead used only git pushes.
Create a tree for your subsystem hacking.
This is the key which you will need for kpd to use.
This will trigger a download of the key using your web browser.
Be mindful and only select the specific repos you want the app to have privileges to.
You will want to add a secret, the private key which you will use to allow the github actions from kdevops to upload to the kdevops-results-archive.
You will want the key to be created with a command like this to be enable the github webfactory ssh agent to know its associated to a specific repo.
You will cat the private key.
And add it to a secrete key.
Now clone kpd on a system you have access to and which is private, this is where kpd will run.
To find your project ID number use the patchwork API page to look for your respective project ID number. So for instance the linux-acpi patchwork project has project ID 2 while the inux-media patchwork project has project ID 4.