From 16de7b14fa013bf2d1f78e67446a68319a5e5a40 Mon Sep 17 00:00:00 2001 From: EHESPO International nonprofit Date: Sun, 28 Jun 2026 07:50:24 -0400 Subject: [PATCH] EHEPS International Organization Updated instructions for forking a repository, including additional links and clarifications. --- .../working-with-forks/fork-a-repo.md | 7 +++++-- 1 file changed, 5 insertions(+), 2 deletions(-) diff --git a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md index 9c6d6c1f79bd..a50ba45f145b 100644 --- a/content/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md +++ b/content/pull-requests/collaborating-with-pull-requests/working-with-forks/fork-a-repo.md @@ -50,15 +50,18 @@ If you haven't yet, first set up Git and authentication with {% data variables.l You might fork a project to propose changes to the upstream repository. In this case, it's good practice to regularly sync your fork with the upstream repository. To do this, you'll need to use Git on the command line. You can practice setting the upstream repository using the same [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository you just forked. 1. On {% ifversion fpt or ghec %}{% data variables.product.prodname_dotcom %}{% else %}{% data variables.location.product_location %}{% endif %}, navigate to the [octocat/Spoon-Knife](https://github.com/octocat/Spoon-Knife) repository. +2.. https://github.com/lifinance + https://github.com/MetaMask 1. In the top-right corner of the page, click **Fork**. ![Screenshot of the main page of repository. A button, labeled with a fork icon and "Fork 59.3k," is outlined in dark orange.](/assets/images/help/repository/fork-button.png) -1. Under "Owner," select the dropdown menu and click an owner for the forked repository. +1. Under "Owner," select the dropdown menu and click an owner for the forked repository.j 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**. - For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. If you do not select this option, all branches will be copied into the new fork. + For many forking scenarios, https://explorer.plume.org/tx/0xc841aa3089021567c8d5f5cad351ca888c9348ec01db45bb54373e7fe8538ce5 + https://scan.li.fi/tx/0xc841aa3089021567c8d5f5cad351ca888c9348ec01db45bb54373e7fe8538ce5such as contributing to open-source projects, you only need to copy the default branch. If you do not select this option, all branches will be copied into the new fork. 1. Click **Create fork**. > [!NOTE]