You can view, sort, and filter the forks of a repository on the repository's forks page. For more information, see " Restoring a deleted repository." If you delete a private repository, all forks of the repository are deleted. After a fork is deleted, you cannot restore the fork. For example, you can add collaborators, rename files, or generate GitHub Pages on the fork without affecting the upstream. You can make any changes you want to your fork, and there will be no effect on the upstream. For more information, see " Allowing changes to a pull request branch created from a fork."ĭeleting a fork will not delete the original upstream repository. You cannot give push permissions to a fork owned by an organization. This speeds up collaboration by allowing repository maintainers to make commits or run tests locally to your pull request branch from a user-owned fork before merging. If you fork a public repository to your personal account, make changes, then open a pull request to propose your changes to the upstream repository, you can give anyone with push access to the upstream repository permission to push changes to your pull request branch (including deleting the branch). In open source projects, forks are often used to iterate on ideas or changes before incorporating the changes into the upstream repository. When you view a forked repository on GitHub, the upstream repository is indicated below the name of the fork. A fork can be owned by either a personal account or an organization. After you fork a repository, you can fetch updates from the upstream repository to keep your fork up to date, and you can propose changes from your fork to the upstream repository with pull requests. In the File menu, click Clone Repository.Forks let you make changes to a project without affecting the original repository, also known as the "upstream" repository. For more information, see " Cloning a repository from GitHub to GitHub Desktop". You can also clone a repository directly from GitHub or GitHub Enterprise. For more information, see " Managing fork behavior". Any existing forks default to contributing changes to their upstream repositories. You can choose to use your fork to contribute to the original upstream repository or to work independently on your own project. When you try to use GitHub Desktop to clone a repository that you do not have write access to, GitHub Desktop will prompt you to create a fork automatically. For more information, see " About forks." You can create a pull request to propose that maintainers incorporate the changes in your fork into the original upstream repository. To make changes without affecting the original project, you can create a separate copy by forking the repository. When you clone a repository, any changes you push to GitHub will affect the original repository. For more information, see " Syncing your branch in GitHub Desktop." If you own a repository or have write permissions, you can sync between the local and remote locations. You can create a local copy of any repository on GitHub that you have access to by cloning the repository. You can clone or fork a repository with GitHub Desktop to create a local repository on your computer. Repositories on GitHub are remote repositories.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |