@@ -33,7 +33,7 @@ This tutorial uses [the Spoon-Knife project](https://github.com/octocat/Spoon-Kn
|
||||
|
||||

|
||||
1. Under "Owner," select the dropdown menu and click an owner for the forked repository.
|
||||
>[!NOTE] If your username is grayed out, it's because the fork already exists. Instead, you should bring your existing fork up to date. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-branch-from-the-web-ui)".
|
||||
>[!NOTE] If your username is grayed out, it's because the fork already exists. Instead, you should bring your existing fork up to date. For more information, see "[AUTOTITLE](/pull-requests/collaborating-with-pull-requests/working-with-forks/syncing-a-fork#syncing-a-fork-branch-from-the-web-ui)."
|
||||
1. By default, forks are named the same as their upstream repositories. Optionally, to further distinguish your fork, in the "Repository name" field, type a name.
|
||||
1. Optionally, in the "Description" field, type a description of your fork.
|
||||
1. Optionally, select **Copy the DEFAULT branch only**.
|
||||
|
||||
@@ -20,7 +20,7 @@ Each gist indicates which forks have activity, making it easy to find interestin
|
||||
|
||||
If you want to make local changes to a gist and push them up to the web, you can clone a gist and make commits the same as you would with any Git repository. For more information, see "[AUTOTITLE](/repositories/creating-and-managing-repositories/cloning-a-repository)."
|
||||
|
||||
To clone a gist, select the Embed dropdown menu, then click Clone via HTTPS or Clone via SSH.
|
||||
To clone a gist, select the Embed dropdown menu, then click **Clone via HTTPS** or **Clone via SSH**.
|
||||
|
||||

|
||||
|
||||
|
||||
Reference in New Issue
Block a user