Pull (fast-forward if possible) fetches any updates on the remote branch, then attempts to fast-forward the local branch. The remote commits display on the graph because they have been fetched,but have not been incorporated into the local repo. Let’s demonstrate what each one does by starting with an example 2 commits made locally, and 2 that have been made on the remote. Pulling first performs a fetch and then incorporates any commits in the remote repository into the local copy. To fast-forward your currently checked out commit, you can right click on the branch with newer commits, and select the Fast-Forward option from the menu. Fast-forwardingįast forwarding moves the currently checked out commit to one that was added later, replaying all commits in between in the order which they happened. You can change this setting from Preferences > General menu. GitKraken Client automatically fetches updates from your remote repositories every minute by default. However if you are both ahead and behind a remote, you will not be able to perform a Pull (fast-forward if possible) as the branches have diverged. It is possible to be both ahead of and behind a remote. If you are ahead of the remote branch, there are local commits that have not yet been pushed to the remote. Pull (fast-forward if possible) to get these changes on local. When you’re behind the remote, it means that there are commits on the remote branch which have not been incorporated into the local repo.
GITKRAKEN CHANGE ORIGIN REPO UPDATE
Updates will appear in the graph, and also update any branches on the left to show how many commits you are ahead or behind.
Pulling and fetching take updates from the remote and get them into our local repo.įetching gets updates from remote branches, but does not update any files in your working directory. You may drag a branch to a remote branch on the graph, or to a remote branch listed in the left panel. Drag and drop to pushĭrag and drop a branch to a remote to access the Push action. This is typically the fork name followed by a slash, and the branch name. If the branch pushed does not exist on the remote, GitKraken Client will prompt you to name and create the new remote branch. Caution: Forcing a push is considered destructive because it overwrites the remote branch by replacing it with the local branch.
0 kommentar(er)
