Remix clone Hacker News

Your key cannot be tied to more than one identity, and if you use GitHub Enterprise, your work identity may be restricted from contributing to repos outside of the Enterprise. This is to prevent cloning private code into public spaces. For this reason, you need to have separate keys.

▲

pestaa 3 months ago | parent [-]

Interesting!

Curious though that the compliance rules are strict enough it warrants distinct keypairs, but not that strict for the devs to use dedicated hardware.

	▲	x3n0ph3n3 3 months ago \| parent [-]
		It's not a compliance rule that requires different keypairs. It's just that GitHub doesn't support using the same keypair for different GitHub users. If you have a GitHub Enterprise user for internal code development, that GitHub Enterprise user is restricted from interacting outside of the GitHub Enterprise/ If you also need to contribute to OSS projects as part of your job, you have to use a different GitHub user, and therefore a different keypair.