Tell HN: Copilot For Business forcibly terminates Copilot Personal subscriptions
My org recently enabled Copilot For Business.
I've had a personal subscription until this point.
Today, my Copilot plugin started throwing rate-limit errors. Upon checking my billing details, I notice I can no longer manage my subscription and that it's managed by my Org.
GitHub Support told me that my personal subscription was cancelled, with a pro-rated refund, because it's not possible to have both a personal and org subscription.
Now I have to wait for someone from the org to manually revoke my seat so I can re-purchase my own subscription.
Heads up for anyone else who finds themselves in this situation.
31 comments
[ 8.6 ms ] story [ 59.4 ms ] threadAlso, did you use the same github account for your personal projects as you did for job purposes?
In my case I just created a new account to use with the org, so that I can control the settings on my personal account.
I just checked the offering today and was confused why the personal subscription is with $10 almost half of the business plan with $19. After some more browsing I found a page which claimed that a business plan had better privacy protection (e.g. your input is not used for training). So the business plan seems to be a tad better.
GitHub encouraging and enabling using the same account for work (-for-hire) and personal (or work, but owned by yourself) might've been great for growth, but it's a risk managment minefield.
I seem to recall Apple doing roughly the same thing with email accounts.
If the org hits their spending limit, you're SOL.
At $JOB, it's mandated to have a separate GitHub account
it's a complete separation of responsibilities in the same way that I have a work laptop and a personal laptop.
Of course, we can’t (or shouldn’t) be uploading any of our code to GitHub for work. We have self-hosted Bitbucket servers. The corporate GitHub accounts are strictly used for Copilot.
If/when I leave the company, I’m pretty sure they don’t want all the code tied to my personal account. That sounds like a nightmare. I don’t want that either.
If you want a personal account and are willing to pay for it, sign up under a non-work account. Use that at home, and use your work account at work. This makes sense to me.
_always_ and I mean _always_ have a separate github/gitlab account for work and private things, otherwise you risk getting a lawsuit of your (former) employers. Especially if your work contract assigns all intellectual property rights to the employer.
Although you _can_ use separate accounts, the idea that you MUST is nonsense.
But yes, I encountered the same thing once I was added to my full-time employer’s GHE Cloud account. So far, not a problem.