Sudden deployment failure from private GitHub repository on Hobby plan

[bck0]

Hi,
Since January this year, I have been regularly deploying both preview and production versions of an NGO educational application, which is intended for use by children in elementary schools.

However, today the deployment suddenly failed with the following error message:
Cannot deploy from a private GitHub organization repository on the Hobby plan.

Has there been a change in policy recently that prevents me from deploying this project? Or is this a bug?

Thanks in advance for your clarification.

Best regards,
bck0

[amyegan]

You’ll be able to deploy your project if you make the repo public or move it to a personal GitHub account.

Deploying private GitHub organization repos has been restricted for as long as I can remember, but a loophole was allowing some to be deployed anyway. A recent update corrected it.

From Deploying private Git repositories using Hobby teams:

You cannot deploy to a Hobby team from a private repository in a GitHub organization, GitLab group, or Bitbucket workspace. Consider making the repository public or upgrading to Pro.

[mnigos]

Why it wasn’t communicated in any way?

[amyegan]

The restriction on Hobby teams deploying from a private repositories in GitHub organizations, GitLab groups, or Bitbucket workspaces is documented at the link posted above. This is not a new limit, just a bugfix.

Note that public repos can be deployed so open source projects can use GitHub organizations, GitLab groups, or Bitbucket workspaces to coordinate.

I hope that makes sense!

[cbehnke-1500 (cbehnke)]

Hi Amy, it might have been an internal policy, but it doesn’t appear to have been communicated externally prior to this. I entered the link you included above into the Internet Archive, and as of the most recent snapshot on June 28th, the quoted policy/limitation did not exist.

[davidnomid]

@amyegan

Deploying private GitHub organization repos has been restricted for as long as I can remember

Can you provide proof of that?

[amyegan]

I’m not here to fight with you, only relaying the rules as I know them. Vercel’s site has gone through multiple updates over the years, so I don’t know all of the places where it was previously documented. But I’ll share what I have.

It used to be on the pricing page (snapshot from May 2020)

There are records of the support team sharing the same info for a while now. Some years before I joined Vercel.

• Can Github organization repos be imported? · vercel/community · Discussion #123 · GitHub
• Cannot add a new project on hobby plan for a repository owned by Github Organization · vercel/community · Discussion #6733 · GitHub

And in guides, like Can I connect a Pro team to a personal Git account? (and snapshot with the same info)

Hope that’s all the proof y’all need

[jacobparis]

Public repos from Github orgs have historically also been restricted, but that restriction has recently been removed