Главная -> Природные Сиськи
A fork is a complete copy of a repository, including all files, commits, and optionally branches.
Forks вероника озабоченная маньячка a great way to support an Inner Source workflow: A fork starts with all the contents of its upstream original repository. Вероника озабоченная маньячка you create a fork, you can choose whether to include all branches or limit to only the default branch.
None of the permissions, policies, or build definitions are applied. The new fork acts as if someone cloned the original repository, then pushed to a new, empty repository.
Вероника озабоченная маньячка a fork has been created, new files, folders, and branches are not shared between the repositories вероника озабоченная маньячка a PR carries them along. You can create PRs in either direction: The most common direction will be from fork to upstream.
For a very small team developerswe recommend working in a single repo. Everyone should work in topic branches, and master should be protected with branch policies. As your team grows larger, you may find yourself outgrowing this arrangement and prefer to switch to a forking workflow. If your repository has a large number of casual or infrequent committers similar to an open source projectwe recommend the forking workflow.
Typically only core contributors to your project have direct commit rights into your repository. You should ask вероника озабоченная маньячка from вероника озабоченная маньячка this core set of people to work from a fork of the repository. Specify a name, and choose the project where you want the fork to be вероника озабоченная маньячка. If the repository contains a lot of topic branches, we recommend you fork only the default branch. You must have the Create Repository permission in your chosen project to create a fork.
We recommend you create a dedicated project for forks where all contributors have the Create Repository permission.
For an example of granting this permission, see Set Git repository permissions. The fork will be your origin remote. Select Save and the new remote is added and displayed in the repository settings. We recommend you still work in a topic branch, though. This allows you to maintain multiple, independent workstreams simultaneously.
Also, it reduces confusion later when you want to sync changes вероника озабоченная маньячка your fork. Make and commit your changes as you normally would. Open a pull request from your fork to the вероника озабоченная маньячка. All the policies, required reviewers, and builds will be applied in the upstream repo.
Once all policies are satisfied, the PR can be completed and the changes become a permanent part of the upstream repo.
Anyone with the Read permission can open a PR to upstream. If a PR build definition is вероника озабоченная маньячка, the build will run against the code introduced in the fork.
Open the Branches page in Team Explorer. Make sure master is checked out.
Вероника озабоченная маньячка new feedback system is built on GitHub Issues. Read about this change in our blog post. Sharing code between forks You can create PRs in either direction: Choosing between branches and forks For a very small team developerswe recommend working in a single repo.
The forking workflow Create a fork Clone it locally Make your changes locally and push them to a branch Create and complete a PR to upstream Sync your fork to the latest from upstream Create the fork Navigate to the repository to fork, and choose Fork. Choose Fork to create the fork.
Note You must have the Create Repository permission in your chosen project to create a fork. Вероника озабоченная маньячка the Settings page. Under Remoteschoose Add.
Add a new remote called upstreamusing the Git clone URL of the repo you forked. On the command line, navigate to your repository, and type: Important Anyone with the Read permission can вероника озабоченная маньячка a PR to upstream.
Open the Synchronization page in Team Explorer. On the command line, navigate to your repository and run: Product feedback Sign in to give documentation feedback Вероника озабоченная маньячка feedback You may also leave feedback directly on GitHub.
There are no open issues.