A personal copy of an application is also called a fork or a per-developer repository. The best practice is for developers to create a fork off the main repository before starting development work. They use the fork to do independent development work and then test the code in the fork before committing those changes back to the main repository.
Note the following:
- You can create a fork only once.
- You update the fork to be synchronized with the main repository.
- If the master repository has any b ranches (versions) at the time you create the fork, all its branches will also be forked.