There have been instances where GitHub has banned users for using an email address from a custom domain. If your account is associated with an enterprise plan the chances of that happening decrease significantly. Also puts you in much better position for recourse
There's a CLI tool that writes the agent skills into the right folder. The other option would be to have everybody manually unzip a download into a folder which they might not remember.
Jenkins CI has a clever feature where every password it injects will be redacted if printed to stdout; `enveil run` could do that with the wrapped process?
Of course that's only a defense against accidents. Nothing prevents encoding base64 or piping to disk.
If you wouldn't use your personal email account on your work computer, I don't see why you wouldn't create a new GitHub account only for work.
reply