Anurag Goel, Is there an updates about this feature? I had to disconnect my account from the Customer's project just to create a new account.

After more thought, the main use case I can think of where this is is if you're trying to deploy private repos from multiple different Render accounts. Since I'm only trying to deploy public repos from different business accounts (mainly so the client is responsible for the costs of deployment and service), simply creating different Render accounts, not connecting Github, and just pasting the URL of the public repo in as the target repo, is enough.

The main drawback is that you can't turn on auto-deploy, but I'm personally not a huge fan of that anyway.

Until this Render feature is implemented (the obviously best solution to the problem), the best workaround I could think of is creating a new Github account for each "client project", creating the repo in that Github, and then sharing the repo with your personal Github so that you can still show an accurate and all-encompassing contribution history without needing to dilute/complicate that history by operating through several single-use Github accounts.

Yep, seeing this as well. I use Render for a project, and am really happy with it, so I advocated for using it on another project with another company, and a part of my first-run experience was hitting this limitation and then needing to join the company's org with my personal email rather than my work email.

Found this out today, as well. This is a pretty big drawback since I use one github account for multiple render projects/orgs.

Stumbled upon this today. I have a single GitHub account but multiple Render accounts (one personal and one for my company). I want to keep Render accounts separate mainly because email addresses are different and on the company one I want it to be connected to my company's Google Workspace.

This would be very helpful.

This is a pretty huge drawback of Render. GitHub encourages users to use a single personal account rather than creating separate accounts for organization use (to maintain your commit history & activity). Since my company uses Render, I'm essentially unable to use it for anything else.

I've run into this problem at two different companies now. I'd really like to avoid creating another GitHub account just for my new company.

Hi (-:

Arriving late to the party.

Maybe I am missing something here, please correct me.

But coming from Heroku this is a H-U-G-E deal breaker.

So in Heroku we multiple users working inside Heroku's dashboard.

All them can create services, jobs and more...

But in Render only a SINGLE user can create services and jobs, and other users are just left out because they are stuck at the "connect to Github" screen.

I must be missing something here, because this the most basic use case coming from Heroku. Maybe I am not seeing a simpler way around this?