JennieOhyoung

There are two sides to this story: one on hand, we should do everything in our power to prevent leaks from happening and on the other, we need to have a mitigation plan to ensure proper take down of all leaked data to minimize impact.

Prevention:

• Transferring the repository and turning a private repository public should both be turned off by the admin.
• The admin should also consider disabling the ability to fork repositories.
• Restrict repository creation is another way to prevent accidental leaks.
• Immediately convert any public repository to private, along with alerting the repository owners of t

JennieOhyoung

What happens when the fork owner leaves the organization?

When a user is removed from the organization, they will lose access to private forks of your organization’s private repositories, but may still have local copies. However, they cannot sync local copies with your organization’s repositories. See https://help.github.com/en/articles/removing-a-member-from-your-organization

What happens when the fork owner gets re-instated?

Their private forks can be restored if the user is reinstated as an organization member within three months of being removed from the organization. See https://help.github.com/en/articles/reinstating-a-former-member-of-your-organization

What happens when the parent repository gets deleted?

• If it's a private repository, all of its private forks will be deleted as well.