Update docs regarding forking on private repos - #2043
Open
KatieB5 wants to merge 1 commit into
Open
Conversation
Following a tech support query, update the documentation to clarify for users that private repos are configured such that forking is not allowed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Following a tech support query, this PR updates the OpenSAFELY documentation to clarify that private repositories cannot be forked, and explains that users can clone the repository instead.
Note to reviewer: I'm unsure whether this is an official policy or rule that we want to enforce and make clear to users. It's stated in the Manual management of research repos policy proposal, in the Notes section, but not in the NHS OpenSAFELY Management of Research Repositories Policy (Internal).