Connect VeriFlow to GitHub

What is available today

VeriFlow does not use a separate GitHub listing or installation screen. The supported path is an OAuth connection followed by per-repository webhook installation. You choose the repositories in VeriFlow, and the connection is stored for your account.

Set up the connection

1. 1

   Start at onboarding

   Open /onboarding and choose Continue with GitHub. VeriFlow starts the GitHub OAuth flow and returns you to repository selection.

2. 2

   Authorize the requested scopes

   Review the GitHub consent screen for repo and admin:repo_hook. These scopes let the signed-in flow load available repositories and create hooks on the repositories you select.

3. 3

   Select repositories

   On /onboarding/select, VeriFlow loads the repositories available to your GitHub account. Search or filter the list, select one or more repositories, then submit Install … webhooks.

4. 4

   Install the repository webhooks

   VeriFlow creates one webhook for each selected repository and persists the per-repository connection. The hook is configured for pull_request and ping events.

5. 5

   Confirm the connection

   On /onboarding/confirm, check the connection status for each repository or use its Ping control to verify the webhook round-trip. The first review trigger is a pull_request delivery.

What happens after connection

The webhook handler processes pull request deliveries when the action is opened, synchronize, or reopened. Open a pull request in a connected repository, or push a new commit to it, to send the supported delivery into VeriFlow.

A ping is for checking the connection itself; it is not the review trigger. The repository must be selected in VeriFlow before its webhook can deliver events to the connection.

Troubleshooting the setup

• OAuth does not start or completes for the wrong account. Return to /onboarding and restart the connection with the GitHub account that can access the repositories you want to select.
• The repository list is empty. Confirm that the authorized GitHub account can access at least one repository, then retry the connection and return to /onboarding/select.
• A webhook cannot be installed. Check that the selected repository is still accessible to the authorized account and retry from repository selection.
• The confirmation stays pending. Use the repository’s Ping control on /onboarding/confirm. If the round-trip still does not complete, return to selection and reinstall the hook for that repository.