The Forking Workflow differs significantly from other Git procedures. Rather than having a single server-side repository to operate as the “central” codebase, Forking Workflow provides each developer their own server-side repository. This approach is most commonly observed in open-source projects that are available to the public.
The major benefit is that contributions may be merged without everyone having to push to a single central repository to keep the project history clean. Only the project maintainer may push to the official repository, and developers can push to their own server-side repositories.
Developers will push their local commits to their own public repositories as soon as they are ready to publish them. Then they’ll submit a pull request from the main repository, notifying the project’s maintainer that an update is ready for integration.