Update: connecting private, organization-owned GitHub repositories

I didnt realise there are two pages. I have found the site causing this notice and deleted it. thanks.

1 Like

We currently have our repos set up to deploy using GitHub actions, looking at the deploys in the Netlify UI, I can see that it says: “Deploy triggered by hook: Prismic Publish”.

I’m a little confused how GitHub contributors are calculated in this instance? Do we need to pay $19 per developer that has made a commit into the published branch, or does it go by the latest person who made a commit to that branch? - Can you clarify this further please?

@sharjeel3 Welcome, and I’m glad you found it!

Also welcome, @AntMo. Deploys with the message “Deploy triggered by hook” were triggered by build hooks and don’t have a Git contributor associated with them.

You can tell when a deploy has a Git user associated with it by visiting the deploy detail page. In the card at the top, it displays the username and avatar of the Git user whose action triggered the deploy:
after the page title and the time of the deploy is the highlighted message, "by notsothorough on GitHub"

Hope that helps. Let me know if you have any other questions!

Hey, y’all, we have an update on timeline. (Head’s up to @mjarrell and @yuhan since you both asked about this earlier. :slight_smile: )

The end of the grace period for sites with existing private, organization-owned repositories is now set for September 30, 2022. After this date, Git-triggered builds for sites connected to these types of repos will fail. All other sites will continue to deploy as normal.

We’ve also updated the Netlify UI and FAQ page with this info.

1 Like

OK, awesome. Thanks for the update. I’ve put in a couple of support requests to see about upgrading our account to a pro account (either through the open-source plan since we host an open-source site or if needed on a yearly payment rather than monthly) but I’m still waiting to hear back on those.

A post was split to a new topic: Not able to deploy Nuxt.js Boilerplate

Hello @douglasrtl, welcome to netlify forums

Don’t ask for help under unrelated threads :slight_smile:
Reason being that nobody will answer and also
just to stay organized :slight_smile:
rather than that make a new topic! Thanks :smiley:

Have a nice rest of your day, doug

2 Likes

Thanks for catching that, @B00bleaTea! I have separated the topics so that they can get the relevant support.

3 Likes

I had a private + org-owned repo but I made it public (and pushed multiple commits) after I got the first announcement about this change. I still had a private + personally-owned (not org) repo that I thought was still allowed; though I received another email today about the change.

Is there any way for me to see whether or not I am compliant with free tier, other than to wait and see if you start charging me?

I just wanted to post an update and say that the support team helped up get moved over to an open source team so I think we’re good to go now! Thanks so much! :blush:

1 Like

If you don’t see any banner in the UI, you’re good to go.

But my point is that I still see the banner but all of my repos are either personal-private, personal-public, or org-public now.

Hi @atuttle, looking through your sites, I found two that our database has marked as having private, org-owned repos. Checking the repos, I see that one actually is a private, org-owned repo and the other seems to need a commit push to update our data.

I’ll DM you with the site names/repos.

Hello!
Thank you for offering us a free plan so far.

After that date (9/30/2022), Git-triggered builds from private, organization-owned repositories will fail on Starter plans.
Git overview | Netlify Docs

This means that
I understand that if we don’t Deploy, the site will remain published on the web, is that correct?

I have the same problem as some stated here, I see the banner “You have one or more sites linked to a private, organization-owned GitHub repository…” but this isn’t the case. All my sites are linked to the same personal github account. Are private repos linked to a personal account also going to pro plan?

Hi @KiichiSugihara and @OlivierSte! Welcome to the support forums.

That is correct. You can also continue to deploy by building locally and deploying manually via CLI, API, or drag & drop.
 

Personal private repos can still be linked for free on the Starter plan. I’ve checked your account and found two sites connected to org-owned private repos. I’ll send you the site and repo names in a DM.

I have the same issue as many others: no idea which of my repos causes the notification.

I went through all the warnings on every repo on every page of the listing and could not find it. I might have already changed the repo visibility or owner in the past but not pushed any updates, as most of my sites are not receiving updates actively.

Why don’t you just send the list of the sites/repos to every client along with the notification email? Or at least me :slight_smile:

Happy to just leave it as it is as I probably won’t trigger new builds for the site anyway, and if I do I’ll get the error then and there. But I don’t want to be in breach of any ToS (nor do I want these warnings, banners or emails either).

Unfortuantely, the email service that we use makes it surprisingly complicated to do this, and the vast majority of affected users have only a few sites.

I can do the “at least just me” part for you, though! :smile: I found one site that uses an org-owned private repo. I’ll send the name to you in DM.

Hello, if I unlink the repo and do manual deploys instead, will I still be able to use Netlify Identity with git-gateway?

@hoangbn good question! Netlify’s hosted Git Gateway service requires a repo to be connected to the site for continuous deployment.

One thing you could do is leave the site connected to your org-owned private repo. Git-triggered deploys to that site will begin failing after September 30, and the UI will display a banner on the site page explaining this, but it will not otherwise affect the operation of your site or other sites in your team.

Git Gateway would still be able make Identity-authorized commits to your repo, but those commits (along with any other commits) wouldn’t be able to trigger deploys. If you want to deploy the site, you’ll need to do so manually.

1 Like