Each self-hosted instance needs its own GitHub App: the app's private key and webhook URL belong to the instance that receives its events, so one shared public app cannot serve other operators' instances.
The dashboard starts GitHub's app manifest flow with archie's permissions (Contents, Issues, Pull requests, Workflows read and write; Checks, Commit statuses, Actions read-only), events and a capture source as the webhook URL prefilled. On return it stores the app ID, private key and webhook secret as secrets and creates the GitHub connection and capture source from them.
Done when an operator goes from no GitHub connection to a working app connection without copying a key or filling in GitHub's form. Relates to #1817.
Each self-hosted instance needs its own GitHub App: the app's private key and webhook URL belong to the instance that receives its events, so one shared public app cannot serve other operators' instances.
The dashboard starts GitHub's app manifest flow with archie's permissions (Contents, Issues, Pull requests, Workflows read and write; Checks, Commit statuses, Actions read-only), events and a capture source as the webhook URL prefilled. On return it stores the app ID, private key and webhook secret as secrets and creates the GitHub connection and capture source from them.
Done when an operator goes from no GitHub connection to a working app connection without copying a key or filling in GitHub's form. Relates to #1817.
sam
added the feature label 2026-11-08 14:03:46 +00:00
sam
added the medium label 2026-11-12 15:51:29 +00:00
sam
added the deferred label 2026-11-15 17:26:11 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Each self-hosted instance needs its own GitHub App: the app's private key and webhook URL belong to the instance that receives its events, so one shared public app cannot serve other operators' instances.
The dashboard starts GitHub's app manifest flow with archie's permissions (Contents, Issues, Pull requests, Workflows read and write; Checks, Commit statuses, Actions read-only), events and a capture source as the webhook URL prefilled. On return it stores the app ID, private key and webhook secret as secrets and creates the GitHub connection and capture source from them.
Done when an operator goes from no GitHub connection to a working app connection without copying a key or filling in GitHub's form. Relates to #1817.