Skip to content

Update docs regarding forking on private repos #2043

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
KatieB5 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Update docs regarding forking on private repos #2043

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions docs/repositories.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -19,6 +19,8 @@ Contact [Tech Support](how-to-get-help.md/#slack) to request that your repositor

If your request is approved, Tech Support will make your repository private and you will be notified once this has been completed.

If your OpenSAFELY repository is made private, other users will not be able to fork the repository. Instead they can make a copy ("clone") of it (see the [GitHub documentation on cloning a repository](https://docs.github.com/en/repositories/creating-and-managing-repositories/cloning-a-repository#about-cloning-a-repository) for more information on this).

Private repositories will be made public after 12 months. Ahead of that, you can make a new request to extend the private visibility period for another 12 months.

!!! info
Expand Down