Page MenuHomePhabricator

Running vagrant git-update does not update remote branch
Open, LowPublic

Description

After running vagrant git-update, git status reports that the local branch is ahead of the remote branch by n commits. This is because run-git-update works by calling "git pull $url", where $url is an HTTPS version of the remote's URL. Instead of fetching updates from the remote for the local branch, this causes git to fetch updates from the the repository specified by $url, and the remote branch is not updated.

A potential solution may be to set the remote's URL to the HTTPS version, run git pull, and then change it back to the original URL (which may be HTTPS or SSH).

The remote branch can be manually updated afterwards by running "git remote update". This needs to be done for each updated branch.


Version: unspecified
Severity: minor

Details

Reference
bz62627

Event Timeline

bzimport raised the priority of this task from to Low.Nov 22 2014, 3:08 AM
bzimport set Reference to bz62627.
bzimport added a subscriber: Unknown Object (MLST).

Change 118653 had a related patch set uploaded by Wctaiwan:
Temporarily change remote URL during git-update

https://gerrit.wikimedia.org/r/118653

Change 118653 merged by jenkins-bot:
Use 'git pull' for non-SSH URLs in run-git-update

https://gerrit.wikimedia.org/r/118653

This is partially fixed with the patch. Remote branches on repositories that don't require authentication are now updated, but the issue remains for SSH remotes.

Bulk unassigning bugs from Ori.