Git Pull Failed Could Not Read From Remote Repository Intellij

Sync with a remote Git repository (fetch, pull, update)

Before y'all tin can share the results of your work by pushing your changes to the upstream, you need to synchronize with the remote repository to make sure your local copy of the project is up to appointment. You can do this in i of the following ways: fetch changes, pull changes, or update your project.

The Git branches popup indicates whether a branch has incoming commits that have not all the same been fetched:

Fetch changes

When you fetch changes from the upstream, all new data from commits that were made since you last synced with the remote repository is downloaded into your local copy. This new data is non integrated into your local files, and changes are not practical to your code.

Fetched changes are stored as a remote branch, which gives y'all a chance to review them before you merge them with your files. Since fetch does non affect your local development surroundings, this is a rubber way to get an update of all changes to a remote repository.

• To fetch changes, from the principal menu choose Git | Fetch.

Update co-operative

Employ update if you demand to sync a specific branch with its remote tracked branch. This is a convenient shortcut for fetching and afterwards applying changes to the selected branch.

• In the Branches popup or in the Branches pane of the Version Control tool window , select a co-operative and choose Update from the context menu.

IntelliJ Thought volition pull changes from the remote branch and will rebase or merge them into the local branch depending on which update method is selected in .

Pull changes

If you demand to get changes into the current co-operative from some other branch instead of its remote tracked co-operative, use pull. When you pull, you lot non only download new information, only also integrate it into your local working re-create of the project.

1. From the master card, choose Git | Pull. The Pull Changes dialog opens:

   

2. If you lot take a multi-repository project, an boosted drop-down appears letting you choose the repository.

3. If you take several remotes defined for your project, select a remote from the list (by default, it is origin).

4. Select the co-operative from which you desire to pull changes into the branch that is currently checked out. By default, the remote branch tracked by the current local branch is selected. If y'all specify a different branch, IntelliJ Thought volition remember your choice and brandish this branch by default in the future.

5. If you need to pull with options, click Modify options and choose from the following:

   • --rebase: after fetching the changes from a remote branch, IntelliJ Idea will rebase local unpushed changes onto the fetched changes.

   • --ff-but: the merge will be resolved only if it is possible to fast-forward.

   • --no-ff: a merge commit volition be created in all cases, even if the merge could exist resolved as a fast-forward.

   • --squash: a unmarried commit with all pulled changes will be created on peak of the current branch.

   • --no-commit: a merge will be performed, merely a merge commit volition not be created so that you tin can inspect the result of the merge before committing.

   See https://git-scm.com/docs/git-pull for details on pull options.

6. Click Pull.

Update your project

If you have several project roots, or want to fetch changes from all branches each time you sync with the remote repository, you may find updating your project a more convenient selection.

When you lot perform the update operation, IntelliJ IDEA fetches changes from all project roots and branches, and merges the tracked remote branches into your local working copy (equivalent to pull).

1. From the main menu, choose VCS | Update Project or press Ctrl+T. The Update Projection dialog opens.

2. Select the update type (this strategy will be applied to all roots that are under Git version command):

   • Merge the incoming changes into the electric current branch: select this pick to perform merge during the update. This is equivalent to running git fetch so git merge, or git pull --no-rebase.

   • Rebase the current co-operative on elevation of the incoming changes: select this option to perform rebase during the update. This is equivalent to running git fetch then git rebase, or git pull --rebase (all local commits volition be put on top of the updated upstream head).

If you choose not to show the Update Project dialog in the futurity, and so want to modify the default update strategy later, go to the Version Control | Confirmation folio of the IDE settings Ctrl+Alt+S, select Update under Display options dialog when these commands are invoked, and modify the update strategy the next time you lot perform an update.

When the update performance is completed, the Update Info tab is added to the Git tool window Alt+9. It lists all commits that were made since the last sync with the remote, and lets you review the changes the same way equally in the Log tab.

Final modified: 12 January 2022

demmerhasked70.blogspot.com

Source: https://www.jetbrains.com/help/idea/sync-with-a-remote-repository.html

Share this post