HackerOne Code
Visit HackerOne.comLog In
  • Introduction to HackerOne Code for On-Premise Integrations
  • Create User Account & Organization
  • Installing PullRequest Proxy
  • Configuring your Proxy to Connect to the PullRequest Server
  • Configure Posting User
    • Configure GitHub Posting User
    • Configure Bitbucket Posting User
    • Configure GitLab Posting User
    • Configure Azure DevOps Posting User
  • Configuring SSL
  • Start the PullRequest Proxy
  • Verify Data on HackerOne Code
  • Configure Webhooks
    • Configure GitHub Webhooks
    • Configure Bitbucket Webhooks
    • Configure GitLab Webhooks
    • Configure Azure DevOps Webhooks
  • Next Steps
    • Project Visibility in the HackerOne Code Dashboard
  • Manually Requesting Validation With Posting User
  • Upgrading PullRequest Proxy
  • PullRequest Proxy Dataflow Diagram
Powered by GitBook
On this page
  • Configure Webhooks
  • Applying on the Organization level
  • Webhook Settings
  • Test Connection
  • Applying on the Repository level
  1. Configure Webhooks

Configure GitHub Webhooks

After the GitHub posting user has been created and the repositories are populating in the HackerOne Code dashboard successfully, the GitHub webhooks can be configured.

PreviousConfigure WebhooksNextConfigure Bitbucket Webhooks

Last updated 27 days ago

Configure Webhooks

GitHub allows webhooks to be configured on the GitHub organization or repository level.

HackerOne strongly recommends configuring webhooks on the Organization level so that new Projects your team creates will be immediately provisioned to use the service without interruption.

Applying on the Organization level

From your GitHub organization page, select the Settings tab, then select Hooks from the sidebar. From here, click Add Webhook to create the webhook.

Webhook Settings

Payload URL

The base URL of your Proxy with the following:

/webhooks/github

Content Type

application/json

OPTIONAL - Add a webhook secret. The secret will be used to sign your webhook requests as they are posted to the proxy:

  • You will need the same webhook secret for all of your organizations/repositories if you add one.

  • This secret must match the WEBHOOK_SECRET field when you configured the proxy.

SSL verification

Events

  • Issue comments

  • Pull requests

  • Pull request reviews

  • Pull request review comments

  • Pushes

  • Repositories

Test Connection

Click the Add webhook button; the webhook should appear in the Webhooks section of the previous page. If you click Edit on the recently created webhook, there should be a successful delivery under Recent Deliveries.

If there was an error, double-check the proxy base is valid and /webhooks/github is added as a path.

Applying on the Repository level

To apply on the repository level, perform the same steps as the organization from the repository page.