Skip to main content
Post

Deploy Previews from forks now require approval on all public repos

Netlify changed Deploy Previews from forks on public repositories so they wait for a team member's approval before building. This applies to previews opened by someone outside your Netlify team, and it's the default Require approval setting.

Before, the sensitive variable policy only held these builds when Netlify detected sensitive environment variables in the project. Without any, anyone who opened a pull or merge request from a fork could trigger a build with no review. Netlify's reason is that a fork's Deploy Preview runs the contributor's code and can use your project's resources and your team's usage.

The policy is now called the untrusted deploys policy. It moved from the environment variables settings to Project configuration, then Developer settings, then Continuous deployment. It has three options:

  • Require approval (default): untrusted deploys wait for a team member to accept or reject them.
  • Build without sensitive variables: untrusted deploys build automatically, but variables identified as sensitive aren't passed to the build.
  • Build without restrictions: untrusted deploys build like any other Deploy Preview.

Projects that already chose one of the two build options keep that setting. Production deploys, branch deploys, and Deploy Previews from your own team members aren't affected. Netlify assumes team members have matched their Netlify team user ID with their Git provider accounts.

If your project gets pull or merge requests from people or bots outside your team, you may see more pending deploy requests at the top of the deploy list. Deploy notifications can tell you when one is waiting for approval.

Loading replies