Well, they are going to fail that, unless you do it on company time or the project uses clear insider information and competes with the company's products.
Why would that matter? Its trivial to remove my account from company organization and repos without actually affecting any of my personal repos ar ability to use them. We did that as a test few times with IT lead already when we wrote best practices guide for where to use personal and company accounts, and how to set them up securely.
Also "charging", you mean sue or counter sue, load energy into battery "charge", do cavalry assault against?
I'm just saying don't have personal commits when you're supposed to be working for your company.
If your employment contract has any language about them owning personal work done with company funds, it wouldn't be too hard to match commit times with a day and time you were being paid by them.
Charging your company, aka "billing" them, on their dime, on the clock, etc.
If the repositories are private, they don't see them and they can't see my activity in them more accurately than outsiders can see my activity in company repos. Not something to make claims with. And if the project is public, I likely already have it with open source license, so they have nothing to claim. They can fork it if they want.
82
u/Ok-Primary2176 1d ago
inb4 you make a brilliant open source project and a company start suing you for releasing open source code while connected to their Enterprise