TerraTrue’s GitHub integration lets you associate pull requests with privacy reviews, so you can verify that products and features are developed exactly as approved.


Step 1: Enable the integration in org settings

To enable the GitHub integration, first go to your org settings and turn on the “Enable GitHub” toggle. Once enabled, you’ll see a URL and Secret to add to your GitHub repositories.

Github's webhook integration page.

Step 2: Configure your GitHub webhooks

An admin of your GitHub account will need to configure a webhook for each repository you’d like to integrate with TerraTrue. For each repository in GitHub, go to Settings > Webhooks > Add Webhook. Then enter the URL and Secret provided by TerraTrue and set the content type to “application/json.” 

Add webhook page.

Finally, update the webhook trigger by choosing “Let me select individual events” under the “Which events would you like to trigger this webhook?” header. Choose “Pull requests” from the available events and make sure all other events are unselected.

Updating webhooks page.

Using the GitHub integration to associate pull requests with launches

To associate a pull request with a launch, add simply add a tag to the description of the pull request with the format TT-<launch number>. For example, if the launch number is 12, then the user should add TT-12 to the description.

Important information about launch tags

  1. Launch tags aren’t case sensitive, so you can use “tt” or “TT”
  2. Launch tags must be on their own line in the description
  3. If you’d like to associate a pull request with multiple launches, you can put them all on the same line separated with commas (e.g., TT-12,TT-16,TT-19)
Pull request page in Github.

In the above example, the pull request description contains four valid tags, so launches 226, 225, 224, and 223 would all be associated with this pull request. However, the first line contains launch tag TT-219 with other text, so it is ignored. 


In the webhook section of each GitHub repository you can view recent webhook requests with their status, request payload, and response:

Recent Deliveries page in Github.

Admins can view this history to find more information about why a particular request failed. By design, the response will give limited information on the failure, but should point us in the right direction. If you have any issues with a webhook request, file a support ticket with the relevant request information and we’ll get back to you soon.