I am trying to add my sub domain name. But getting an error
I read [Support Guide] "another site is using this domain" Verifying domain ownership for Netlify production domain as well
I am adding a TXT RECORD with verified-for-netlify with value help.135270 (135270 from page url of
current help page Help Me Register My Custom Subdomain, Getting Error)
Please resolve this issue, by verifying the email
The domain has been removed from the other account.
thank you for your support.
I had one more query before switching to the pro plan. Not sure if this is the right place to ask, it would be helpful if you could clarify.
So the project I am working has some contributors who occasionaly contribute to the project. So will I be charged $19 per contributor automatically, or can I chose who triggers who is allowed to trigger builds. Its one of the things holding me back from subscribing to the pro plan (compared to vercel, which I am currently using)
In Short I want to know if I can have git contributors who can trigger build deploys on code push to the main branch without an extra $19 per contributor /month
Thank You
Hi @shubhamandoda,
Great question!
Part 1 of the answer is to not switch the option to auto-approve deploys from non-team members from the default setting of “requires approval” to “auto-approve” (This is found under team settings => Access and Security)
What you’ll see in the UI for builds triggered by non-approved team members is a deploy that says “pending approval.” If you do not approve the build, it will not complete and you will not be charged. If you manually approve the build, then the Git Contributor will be added to your account as an approved Git Contributor and you will be charged for them. There’s a message that comes up confirming the approval that mentions that you will be charged.
Part 2 of the answer is that Netlify only intends to charge you for team seats for builds triggered by commits we build directly from git notifications from your git provider. While we will not be able to provide tech support on how to work around our pricing system, some workflows that will not add to your account’s seat count include:
- Configuring Netlify not to build non-production branches for your site(s). If teammates only commit to those branches, they will not trigger builds and thus will not require seats on your Netlify team.
- Configuring Netlify not to build Pull Requests/Merge Requests for your site(s). Note that the user who merges a PR or MR will be counted as Netlify team seats; users who have commits in the PR will not be.
- All commits on public repositories (aka: non-private repos) should all build without costing extra team members or requiring any configuration change.
- You can remove current team members who do not need access to our UI. This way you only need to pay for a seat in the months an individual makes a commit.
- Finally, for more tips on optimizing which builds happen on Netlify, we have an article around configuring builds in our Support Forums that might be of interest.
Two additional notes about Git Contributor charges:
- One of the primary differences between a Git Contributor and a full team member is that a full team member always costs $19/month. We only charge you $19 for a Git Contributor if they deploy during a billing cycle. If they don’t deploy, they are considered inactive and do not incur charges.
- You mentioned upgrading to Pro. If you do invite additional full team members to the team and they also contribute from git (creating a Git Contributor) you can match them to the Git Contributor and that will make them count as one user for billing purposes. You can match one Git Contributor to a Netlify team member per Git provider (Github, Gitlab, Bitbucket, ADO.)
I hope this helps!
For now it should be fine as the repositories are public. Also in future if this becomes a problem then your tips on disabling it for PR and deploying via netlify CLI(in CI) should be an option.
Thank you for your descriptive answer and your support.