Hey folks, I’m in a pickle and need some advice. I’m a PowerShell expert in my company. No one else really gets it. I keep all my work scripts on our shared drive, super well-documented and commented.
I’ve got this big private GitHub repo with my personal how-tos that I sometimes check when working. Now, I’m taking a few months off, and my boss is freaking out. He wants access to my personal GitHub account to ‘check for company secrets’. He’s even asking me to download everything to the shared drive and delete my repo!
This feels totally wrong. It’s like he’s asking to snoop through my personal stuff. Plus, I’ve done some side gigs on weekends, and I don’t want him seeing that work.
Is this normal? Can they really ask for my personal GitHub login? What should I do? Help!
As someone who’s navigated the corporate tech world for years, I can say with certainty that your employer’s demand is inappropriate and potentially illegal. Your personal GitHub account is just that - personal. It’s not company property, regardless of your position or expertise.
I’d suggest documenting all work-related scripts and processes thoroughly on company systems before your leave. This demonstrates your professionalism and addresses their concerns about knowledge transfer. If pressed, offer to review the shared drive contents with your boss to ensure everything work-related is accounted for.
If they continue to insist, consider escalating to HR or seeking legal counsel. Remember, protecting your personal intellectual property and privacy is crucial. Don’t compromise on this - it sets a dangerous precedent for you and your colleagues.
I’ve been in a similar situation, and it’s definitely not cool for your employer to demand access to your personal GitHub account. That’s crossing a major boundary.
In my experience, the best approach is to have a frank discussion with your boss about the separation between work and personal projects. Explain that your private repo contains personal and non-work-related code, and giving access would be a privacy violation.
If they’re worried about losing access to work-related scripts, offer to do a thorough review of the shared drive to ensure all necessary documentation and code is there before you leave. You could also consider creating a separate work-specific GitHub account if they want things version-controlled.
Remember, your personal GitHub is your property. Stand your ground politely but firmly. If they persist, it might be worth talking to HR or seeking legal advice. Don’t let them bully you into compromising your privacy.