Skip to content
FIRERUN.

The BaaS & deploy-platform newsroom for builders

Subscribe

Netlify

Netlify Fork Deploy Previews Now Wait for Approval on Public Repos

Check the deploy list on public-repo Netlify projects: pull requests from forks by non-team members now sit pending until a team member approves the build.

Hand-drawn editorial illustration for "Netlify Fork Deploy Previews Now Wait for Approval on Public Repos"

Netlify projects connected to public repositories no longer build a Deploy Preview for a fork’s pull request until a team member approves it, a default that now applies whether or not the project holds sensitive environment variables (Netlify changelog, Nov. 16, 2026).

What Changed

Netlify replaced its sensitive variable policy with what it calls the untrusted deploys policy. The old policy held a fork’s build only when Netlify detected sensitive environment variables on the project. On a project without them, anyone who opened a pull or merge request got a build right away.

Under the new policy, a Deploy Preview opened from a fork by a person outside the Netlify team waits for a team member to accept or reject it. That is the behavior on any project still set to the default, Require approval. Netlify said production deploys, branch deploys and Deploy Previews from team members are unaffected.

Projects already set to one of the other two options keep that choice:

  • Build without sensitive variables: untrusted deploys build automatically and sensitive variables are withheld from the build.
  • Build without restrictions: untrusted deploys build like any other Deploy Preview.

The setting also moved. It was under environment variable settings and now sits at Project configuration > Developer settings > Continuous deployment > Untrusted deploys policy.

Why Netlify Did It

Netlify’s stated reason is cost and control. Building a fork’s preview runs code from an outside contributor, the changelog said, and that code can use the project’s resources and the team’s usage. Approval gives the team a chance to read the change first.

What to Do

Open-source maintainers feel this first. Netlify said affected projects are the ones that receive pull or merge requests from people or bots outside the team, and that they may see more pending deploy requests at the top of the deploy list.

Link every maintainer’s Git account first. Netlify decides who is trusted by assuming team members have matched their Netlify user IDs with their Git provider accounts, and an unlinked maintainer’s fork can be held like a stranger’s.

Turn on a deploy notification next. Netlify points to deploy notifications as the way to learn a deploy is waiting. A held preview otherwise sits in the dashboard until a team member looks.

Then choose the policy on purpose. A docs site with no secrets and a busy contributor base can switch to Build without sensitive variables and get automatic previews back. Netlify said teams can change the option at any time.

The Take

This is Firerun’s read, not Netlify’s. The old rule protected secrets and left build minutes open to anyone who could fork the repository. The new default closes that gap. The cost is friction on the projects that depend on drive-by contributions, where a preview link in the pull request is how reviewers judge a docs or UI change. Netlify’s wording counts bots as outsiders too, so a bot that opens pull requests from a fork will queue up approvals until a team member changes the setting.

Separately, Netlify said in a Nov. 17 changelog post that CLI version 27.18.0 stores login tokens in the operating system’s keychain instead of a plain-text config file. It told users to update every global install, because an older copy can move credentials back to plain text.

Stay in the loop

Get new articles in your inbox

We'll only email you when a new article drops. Unsubscribe anytime.