We recently started using a fork of our repository and opening pull requests from it into the original repository. We noticed that in these pull requests from the fork, Netlify always makes us manually approve the preview deploys. Even after a contributor’s PR was approved in the past, their future PRs still need this manual approval.
Is there a way to whitelist github users or repo forks so that we don’t have to approve them for each PR?
The setting for this can be found on the page below (but you must replace <team slug here> with your actual team slug):
https://app.netlify.com/teams/<team slug here>/settings/access#auto-approve-deploys-from-non-team-members
I’ve seen that setting. that auto-approves any users who open a PR and bills us for them. this is an open source repo so that won’t work for us. is there no way to add specific users?
hey @artw7 thanks for following up!
Even after a contributor’s PR was approved in the past, their future PRs still need this manual approval.
Can you advise whether you’re referring to active or inactive Git contributors here? Even if you’ve got your Deploy Requests set to Require Approval, you shouldn’t need to approve subsequent deploys for the same active Git Contributor - please let us know if that is indeed not the case and we can continue digging on our end!
Hmm, for us this page doesn’t seem to have that option, and we’ve had an author who has committed to the repo before, and they’re still not getting approved.
Likewise, this link
https://app.netlify.com/sites/<team-name>/configuration/deploys#sensitive-variable-policy) here doesn’t lead to a sensitive-variable-policy either.
Could you differentiate active and inactive contributors?
hello @psi 
thanks for reaching out and asking! Active and Inactive Git Contributors are differentiated based on their activity during a billing period in Netlify.
An Active Git Contributor is a non-team member who has been added to the team and has triggered a build, deploy, or Deploy Preview through Netlify from a private Git repository during the current billing period. Active Git Contributors contribute to your total member count and if you are on a Core Pro or Enterprise plan, you will be charged for them. They appear on the Members page as Active Git Contributors.
An Inactive Git Contributor, on the other hand, is a Git Contributor who hasn’t collaborated on any of your team’s sites during a billing period. They will be marked as inactive and you will not be charged for them. You can remove inactive Git Contributors from your team if needed.