When you leave Stanford, the future of your GitHub repository depends on various factors, such as ownership, permissions, and the policies of your organization.
Here are some common scenarios:
- Personal Repository: If the repository is under your personal GitHub account, you retain full control and ownership. You can decide whether to keep it public or private, transfer ownership, or delete it.
Note: It is your responsibility to transfer ownership of your personal repository before your SUNet ID expires. - Organization Repository: If the repository is under Stanford's GitHub organization, the organization retains ownership. Once you leave, your access may be revoked based on Stanford policies. Your contributions remain, but your account may no longer have access to the repository. The repository itself will continue to exist and can be maintained by other team members or new hires.
- Transfer of Ownership: In some cases, you may negotiate the transfer of repository ownership if appropriate and agreed upon by Stanford.
- Forks: If you've forked a repository from Stanford's organization to your personal account, your fork will remain unless you delete it. However, your fork will no longer be able to sync changes from the original repository if your access is revoked.
Be mindful of any intellectual property agreements or non-compete clauses you may have signed, as these could impact your ability to use or share the code after leaving Stanford. Ensure you communicate with Stanford's IT or GitHub admin team to understand their policies regarding your access to repositories after departure.
