Why GitHub canceled the Fork function

GitHub is a code hosting platform for open source and private software projects. Its Fork function is one of its most important functions. Fork means copying someone else's project to your own account. This is a commonly used collaboration method. Users can create a branch under their own account, modify, enhance, repair, etc. the project, and then submit the modified code back to the original project.

However, GitHub recently announced that it will cancel the Fork function. This news has attracted widespread attention and discussion, and many people have expressed concerns and doubts about it. So, why did GitHub cancel the Fork function? What are the impacts on users?

First of all, GitHub canceled the Fork function to strengthen the protection of project contributors. In the past, we could easily fork a project and start modifying it without the consent of the original project owner, and even if the original project owner asked to delete the fork, it would be difficult to do so. In this case, users can make any modifications, additions, deletions, etc. to the Fork project, and finally submit it back to the original project, resulting in the project's contributors and owners losing control of the project. Therefore, in order to protect project owners, GitHub will cancel the Fork function and launch a series of new collaboration methods to improve the security and stability of the project.

Secondly, GitHub's cancellation of the Fork function may cause some inconvenience to users who contribute in this way. However, GitHub has provided other collaboration methods for these users, including:

1. Pull Request: initiate a Pull Request (referred to as PR) on the page of the original project, and submit the modified code back through PR For the original project, the project owner or manager decides whether to accept the modification;
2. Collaborators: Add the users who need to modify the project as Collaborators and give them write permissions to the original project, so that they can directly modify the original project;
3. Branch Protection: Protect a specific branch of the original project, only allow specific users to submit modifications, and impose restrictions on submissions.

So, if you are a GitHub user and need to Fork a project, then GitHub has now provided you with a more flexible and secure way to collaborate.

Finally, GitHub’s cancellation of the Fork function is a positive change. Although this will cause inconvenience to some users, it also better protects the interests of project owners and contributors. Although this measure will take some getting used to, we should have confidence in the new approach under GitHub that the platform is moving in a healthier and more stable direction.

The above is the detailed content of Why GitHub canceled the Fork function. For more information, please follow other related articles on the PHP Chinese website!