Updated GitHub desktop fork instructions #36172
Conversation
…atch the latest github desktop flow
…p-fork-instructions
Co-authored-by: Steve Ward <[email protected]>
This reverts commit dbdeef4.
…p-fork-instructions
|
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
bot
added
the
triage
👓 Previews for changed contentThis comment is 🤖 automatically generated and will be overwritten every time changes are committed to this branch. The table contains an overview of files in the Content directory changesYou may find it useful to copy this table into the pull request summary. There you can edit it to share links to important articles or changes and to give a high-level overview of how the changes in your pull request support the overall goals of the pull request.
Key: fpt: Free, Pro, Team; ghec: GitHub Enterprise Cloud; ghes: GitHub Enterprise Server |
Features the Windows screenshot instead of the Mac one to match the others appearing in the "fork-a-repo" reusable.
|
Which naming style is preferred: "url" or "url-tab"? |
isaacmbrown
added
waiting for review
|
@warp-core 👋 Thanks for the PR and linking to the @steveward If you have time, I'm wondering if you're up for reviewing this since you have the context from the issue. No worries if not, I'll leave it on a board so anyone can pick it up. |
|
@isaacmbrown Will do! @warp-core I'll take a look at this and will get back to you soon. Thanks for the PR! |
There was a problem hiding this comment.
Thanks again for putting this PR together @warp-core. I suggested a few minor changes. Once those are made I'll take a final look and we can get this merged.
| @@ -18,7 +18,7 @@ You can create a local copy of any repository on {% data variables.product.githu | |||
|
|
|||
| When you clone a repository, any changes you push to {% data variables.product.github %} will affect the original repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. For more information, see [AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/about-forks). | |||
|
|
|||
| When you try to use {% data variables.product.prodname_desktop %} to clone a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork automatically. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see [Managing fork behavior](#managing-fork-behavior). | |||
| When you use {% data variables.product.prodname_desktop %} to push new commits to a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see [Managing fork behavior](#managing-fork-behavior). | |||
There was a problem hiding this comment.
| When you use {% data variables.product.prodname_desktop %} to push new commits to a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see [Managing fork behavior](#managing-fork-behavior). | |
| When you use {% data variables.product.prodname_desktop %} to push a change to a repository that you do not have write access to, {% data variables.product.prodname_desktop %} will prompt you to create a fork. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. Any existing forks default to contributing changes to their upstream repositories. You can modify this choice at any time. For more information, see [Managing fork behavior](#managing-fork-behavior). |
| @@ -1,8 +1,9 @@ | |||
| In {% data variables.product.prodname_desktop %}, if you attempt to clone a repository that you don't have write access to, a fork is automatically created for you. | |||
| In {% data variables.product.prodname_desktop %}, if you clone a repository that you don't have write access to, and then attempt to push new commits to the repository, a fork will be created for you. | |||
There was a problem hiding this comment.
| In {% data variables.product.prodname_desktop %}, if you clone a repository that you don't have write access to, and then attempt to push new commits to the repository, a fork will be created for you. | |
| In {% data variables.product.prodname_desktop %}, if you clone a repository that you don not have write access to, and then attempt to push a change to the repository, a fork will be created for you. |
| @@ -0,0 +1,3 @@ | |||
| 1. To create a fork, attempt to write a change to the repository. For example, create a new branch and publish it. A prompt will appear asking if you want to fork this repository. Click "Fork this repository" | |||
There was a problem hiding this comment.
| 1. To create a fork, attempt to write a change to the repository. For example, create a new branch and publish it. A prompt will appear asking if you want to fork this repository. Click "Fork this repository" | |
| 1. To create a fork, attempt to push a change to the repository. For example, create a new branch and publish it. A prompt will appear asking if you want to fork this repository. |
| @@ -0,0 +1,3 @@ | |||
| 1. Click the tab that corresponds to the location of the repository you want to clone. In this example, we click on the URL tab. | |||
|
|
|||
|  | |||
There was a problem hiding this comment.
|  | |
|  |
Most of this description, and most of the changes here, are from #34151, I just made the changes requested in the last review that PR received before being closed.
Why: The current fork instructions for Github desktop were out of date with the latest Github desktop.
Closes: desktop/desktop#13165 (I realize this is an issue from a different repository, however in the comment thread of that issue you will see people mentioning that the issue arises because the docs here need updating.)
What's being changed (if available, include any code snippets, screenshots, or gifs): Minor documentation changes, inluding updating screenshots. The easiest way to see the changes would be to look at the PRs file changes.
Check off the following: