Skip to content

Commit 2d9a572

Browse files
authored
Merge pull request #2043 from opensafely/KatieB5/clarify-no-forking-on-private-repos
Update docs regarding forking on private repos
2 parents d75d0c4 + 6d54a06 commit 2d9a572

1 file changed

Lines changed: 2 additions & 0 deletions

File tree

docs/repositories.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -19,6 +19,8 @@ Contact [Tech Support](how-to-get-help.md/#slack) to request that your repositor
1919

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

22+
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).
23+
2224
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.
2325

2426
!!! info

0 commit comments

Comments
 (0)