Skip to content

Update you-can-fork.md #18960

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.

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

Closed
wants to merge 1 commit into from
Closed

Update you-can-fork.md #18960

wants to merge 1 commit into from

Conversation

timothy-kodes
Copy link

Fix grammar mistake from 'to' -> 'from'

Why:

Closes [issue link]

What's being changed (if available, include any code snippets, screenshots, or gifs):

Check off the following:

  • I have reviewed my changes in staging (look for the "Automatically generated comment" and click the links in the "Preview" column to view your latest changes).
  • For content changes, I have completed the self-review checklist.

Writer impact (This section is for GitHub staff members only):

  • This pull request impacts the contribution experience
    • I have added the 'writer impact' label
    • I have added a description and/or a video demo of the changes below (e.g. a "before and after video")

Fix grammar mistake from 'to' -> 'from'
@welcome
Copy link

welcome bot commented Jul 9, 2022

Thanks for opening this pull request! A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

@github-actions github-actions bot added the triage Do not begin working on this issue until triaged by the team label Jul 9, 2022
@cmwilson21
Copy link
Contributor

@dancingMonkey Thanks so much for opening a PR! I'll get this triaged for review ⚡

@cmwilson21 cmwilson21 added content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review and removed triage Do not begin working on this issue until triaged by the team labels Jul 11, 2022
@jules-p
Copy link
Contributor

jules-p commented Jul 13, 2022

Hi @dancingMonkey 👋🏻 thank you for contributing, we really appreciate it ✨

In this instance, the original wording is actually correct. When you select a repository to fork, you are given the option of forking it to (i.e. making a copy of it in) your own personal account, or forking it to an organization (where you have the necessary permissions). If the repository you are trying to fork is private, then you will be prevented from forking it to an organization account which uses the free plan.

The good news is that you can fork private repositories from organizations which use the free plan, as long as the Allow forking of private repositories setting has been enabled for the organization in question. Any admin of an organization can update that setting by following the steps outlined in Managing the forking policy for your organization.

I'll go ahead and close this pull request for now, but again, thank you for taking the time to contribute!

@jules-p jules-p closed this Jul 13, 2022
@timothy-kodes
Copy link
Author

timothy-kodes commented Jul 13, 2022

Ah I see, thanks for clearing that up and the extra information. @jules-p

@timothy-kodes timothy-kodes deleted the patch-2 branch July 13, 2022 17:38
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
content This issue or pull request belongs to the Docs Content team waiting for review Issue/PR is waiting for a writer's review
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants