Unable to Connect GitHub Repository to Multiple Supabase Accounts Using a Single GitHub Account

[nyxb]

Hello Supabase Team,

I am experiencing an issue with the GitHub integration across different Supabase accounts. Here are the details:

Accounts Involved: I have both a private and a business Supabase account.
Current Configuration: My business Supabase account is successfully connected to my GitHub account. This integration works perfectly, and I can link repositories without any issues.
Issue Description: However, when I attempt to connect a GitHub repository to my private Supabase account using the same GitHub account, the process fails. Specifically, the browser attempts to connect but just reloads the page and continues to display "Connecting GitHub" without completing the action.
Troubleshooting Done: I tested connecting a different GitHub account to my private Supabase account, and this was successful. It appears the issue arises only when trying to use the same GitHub account to link repositories across different Supabase accounts.
From the above, it seems there might be a limitation or a bug preventing a single GitHub account from being used to connect repositories to multiple Supabase accounts. Could you please confirm if this is expected behavior or a potential oversight? Any guidance on how to resolve or work around this issue would be greatly appreciated.

Thank you for your assistance!

Best regards,
@nyxb

[Hallidayo]

Hi @nyxb - When you see the Connecting GitHub do you see any errors in the browser console?

[nyxb]

Hi @nyxb - When you see the Connecting GitHub do you see any errors in the browser console?

Yes sry,

when I log out I get to the auth window but then the same thing happens again no connection. I have also tried it in different browsers. Even after I have deleted all cookies so I have already gone through the standard stuff

NyxbShot-2024-05-27-at-23.34.54.mp4

[Hallidayo]

Hi @nyxb - Odd one, I've tried the same as you but on Chrome and I'm able to connect. Could you try on Chrome so we can rule out if its browser specific?

[nyxb]

Hi @nyxb - Odd one, I've tried the same as you but on Chrome and I'm able to connect. Could you try on Chrome so we can rule out if its browser specific?

I have tested it with arc which is Chrome based and also with Chrome and still have the problem.

[kamilogorek]

@nyxb it's a bug on our side. We had a unique constraint on not only Supabase user id, but also GitHub user id. There's no reason to do that though, and only constraint we need is to have a single authorization per Supabase user.
PR is already pending, should be deployed by tomorrow.

[nyxb]

@nyxb it's a bug on our side. We had a unique constraint on not only Supabase user id, but also GitHub user id. There's no reason to do that though, and only constraint we need is to have a single authorization per Supabase user.

PR is already pending, should be deployed by tomorrow.

Ok I know, very good then it will work soon. Thanks for the info

[kamilogorek]

A fix has been deployed and verified in production. Should be working fine for you now. Thanks for reporting the issue!

[nyxb]

A fix has been deployed and verified in production. Should be working fine for you now. Thanks for reporting the issue!

yes wonderfull now its work :)