What is forking?

The "fork" concept comes from GitHub's workflow and refers to the process of creating an exact copy of someone else's public repository. This copy remains linked to the original, allowing access to its history and content up until the point of the fork. Here you will learn how to fork repositories and what that implies.

Joaquín MontesLast Updated August 09, 2024

Forking differs from duplicating in that it is typically reserved for repositories where you lack access permissions. When you fork a repository, you create a loose connection to the original, preserving its entire commit history. This allows you to use the existing content as a starting point for your own content development.

BaseHub Templates, for example, utilize this feature to generate the template copy in your team.

How to fork a repository

You should look for the

Fork
either in the editor or on the repositories list in the public team view. Upon selecting the icon, you can choose the destination for the fork and decide whether to preserve the commit history. If this option is left unchecked, the new fork will wrap all content in one “initial commit”.

Once the forking process finishes, you will be redirected to your new repository and be able to start writing new content right away.

Remember only public repositories can be forked, learn how to update your repository privacy settings here.<repo settings link here>

Bookmarks

The bookmark feature is a convenient way to keep track of repositories you find interesting or might want to revisit later. When you bookmark

Bookmark Icon
a repository, it will appear in a special list within your personal team on the dashboard’s right panel, allowing for quick and direct access whenever needed.

Related Articles

Did this answer your question?
BaseHub Help CenterBaseHub Help Center© BaseHub Corp. All rights reserved.