I’ve been getting these messages… even though I have a personal Github account. There was one old site that was linked to a separate org account, which I’ve now deleted. But there’s a bunch of other flagged items on my Netlify UI, most of which are public repos anyways… can someone look into this?
@xurxe sure thing! Looking up the account associated with your forum email address, I find one site connected to an org-owned private repo. I’ll DM you the site name and repo.
@xurxe Scratch that! It looks like the one site was deleted very recently, after the data was collected for the most recent email. Your Netlify UI should no longer show a message, and you should receive no more emails.
Hi! I have one netlify account with two sites. One is connected to a personal github account, the other to an org account, but both repos are public. I keep getting emails saying builds will fail for one of these unless I upgrade, but I don’t have any private repos connected to netlify. Can you help? Thanks!
Hi @webakimbo, I can see that your org-owned repo is public, but our database still shows it as private. Did you change the repo visibility recently?
Our database updates repo settings when we receive a new Git deploy hook. In order to update the settings, you’ll need to push a commit to the repo (could be in a PR) so that it triggers a deploy on Netlify. If you like, you can cancel the deploy as soon as it starts, because the database us updated as soon as the deploy hook is received.
Hope that helps!
Seemed to work. Thanks!
2 Likes
hi @verythorough - i have changed our repo to public, but still got the email saying we are at risk of disconnection. could i please trouble you to have a look - super appreciated thank you so much!
you guys have a really good service, its invaluable to a tiny startup like ours and very much appreciated!
Hi, @marketing-dandelions. After making the repo changes, please trigger a new deploy of the site.
It is during the site “build & deploy” process that the repository is checked for compliance.
However, if triggering a new build does not resolve this, please let us know with a reply here and we’ll research the issue to find the cause.
Hi @marketing-dandelions, I do see that the repo connected to your site is now public, but our database still shows it as private.
As @luke noted, this is because you need to trigger a deploy in order for us to receive the settings update from GitHub.
And specifically, you need to push a commit to trigger the deploy. This is because we receive the repo settings information in the deploy hook sent from GitHub. If you like, you can cancel the deploy after it starts, because our buildbot updates the database as soon as the hook is received.
hi @verythorough - thank you so much for the assistance. we have done a deploy and it seems to have worked! can you please confirm it shows as public on your side too now - super appreciated. Thanks so much!
1 Like
@marketing-dandelions Yes, it’s marked as public now!
1 Like
@luke @verythorough you guys were super helpful and this worked with no problems. Very much appreciate the support!
1 Like