From c89cd32ba2d03b74bf40118aade447ebb9bb9678 Mon Sep 17 00:00:00 2001 From: mseger-statsig <101903926+mseger-statsig@users.noreply.github.com> Date: Tue, 12 Aug 2025 16:43:41 -0700 Subject: [PATCH 1/2] Pre-commit Webhooks v1 --- docs/guides/setting-up-reviews.md | 13 +++++++++++++ 1 file changed, 13 insertions(+) diff --git a/docs/guides/setting-up-reviews.md b/docs/guides/setting-up-reviews.md index a01e091fb..04973e5b5 100644 --- a/docs/guides/setting-up-reviews.md +++ b/docs/guides/setting-up-reviews.md @@ -57,3 +57,16 @@ By default if you have turned on "Reviews Required" for your Project, reviews wi ![Screen Shot 2023-04-11 at 9 47 12 AM](https://user-images.githubusercontent.com/101903926/231233087-5b87310d-b33b-456e-b1a7-7a73555c8100.png) ![Screen Shot 2023-04-11 at 9 48 02 AM](https://user-images.githubusercontent.com/101903926/231233356-967c9785-5a89-4cac-a04a-e3f11cb7bb12.png) + +### Configuring Custom Approval Workflows (Pre-commit Webhooks) +If you prefer to leverage an internal approvals workflow or, for example, want to run proposed config changes through a suite of automated tests before they go live, you can leverage **Pre-commit Webhooks**. Pre-commit Webhooks enable you to listen for config changes on the Statsig side, route those changes through internal approval processes, test suites, etc. and then leverage Console API to send back either a review approval or rejection before final changes can be committed. + +To set up the webhook itself, navigate to **Settings** -> **Integrations** -> **Webhook**. +Screen Shot 2025-08-12 at 4 28 12 PM + +To configure the Pre-commit Webhook experience for Statsig Console users, navigate to **Settings** -> **General**, where you will be able to configure the "Pending State" banner text, URL, and a Pre-commit Webhook key for verification purposes. + +Now, when a change is made in the Statsig Console, Statsig hits the customer’s configured webhook with the proposed changes. The change in Statsig will be pending until the customer approves the review via Console API (after their internal checks are complete). Statsig exposes an option for Project Admins (only) to bypass this process and commit the changes directly. + + + From 4877ae0230e6b1aa28c7be2b4982eb4e749c4cdf Mon Sep 17 00:00:00 2001 From: mseger-statsig <101903926+mseger-statsig@users.noreply.github.com> Date: Mon, 25 Aug 2025 10:08:55 -0700 Subject: [PATCH 2/2] Precommit Webhooks v2 Final tweaks w/ Console API --- docs/guides/setting-up-reviews.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/docs/guides/setting-up-reviews.md b/docs/guides/setting-up-reviews.md index 04973e5b5..d2ea825fe 100644 --- a/docs/guides/setting-up-reviews.md +++ b/docs/guides/setting-up-reviews.md @@ -64,7 +64,9 @@ If you prefer to leverage an internal approvals workflow or, for example, want t To set up the webhook itself, navigate to **Settings** -> **Integrations** -> **Webhook**. Screen Shot 2025-08-12 at 4 28 12 PM -To configure the Pre-commit Webhook experience for Statsig Console users, navigate to **Settings** -> **General**, where you will be able to configure the "Pending State" banner text, URL, and a Pre-commit Webhook key for verification purposes. +To enable the Pre-commit Webhook experience: +1. Configure change validations via Console API, see documentation [here](https://docs.statsig.com/console-api/change-validation/). +2. Configure the experience for Statsig Console users via **Settings** -> **General**, where you will be able to configure the "Pending State" banner text, URL, and a Pre-commit Webhook key for verification purposes. Now, when a change is made in the Statsig Console, Statsig hits the customer’s configured webhook with the proposed changes. The change in Statsig will be pending until the customer approves the review via Console API (after their internal checks are complete). Statsig exposes an option for Project Admins (only) to bypass this process and commit the changes directly.