Forking

A fork is a copy of a repository. Forking a repository allows you to freely experiment with changes without affecting the original project.

Most commonly, forks are used to either propose changes to someone else’s project to which you do not have write access, or to use someone else’s project as a starting point for your own idea. You can fork a repository to create a copy of the repository and make changes without affecting the upstream repository.

Propose changes to our official repository

For example, you can use forks to propose changes related to fixing a bug. Rather than just reporting an issue for a bug you have found, you may also:

• Fork the official Intersect Engine repository.
• Make the fix.
• Submit a pull request to the official Intersect Engine repository.

Forking our official repository

You might fork a project to propose changes to the upstream, or original, repository. In this case, it’s good practice to regularly sync your fork with the upstream repository.

1. On GitHub.com, navigate to the AscensionGameDev/Intersect-Engine repository.

2. In the top-right corner of the page, click Fork.

   

3. Select an owner for the forked repository.

   

4. By default, forks are named the same as their parent repositories. You can change the name of the fork to distinguish it further.

   

5. Optionally, add a description of your fork.

   

6. Choose whether to copy only the default branch or all branches to the new fork. For many forking scenarios, such as contributing to open-source projects, you only need to copy the default branch. By default, only the default branch is copied.

   

7. Click Create fork.

   

Note: If you want to copy additional branches from the parent repository, you can do so from the Branches page.

Forking with GitHub CLI

To create a fork of a repository, use the gh repo fork subcommand.

gh repo fork repository

To learn more about GitHub CLI, see “About GitHub CLI” (Github Docs)