mirror of
https://we.phorge.it/source/phorge.git
synced 2024-11-22 14:52:41 +01:00
Stop populating or updating working copies in observed Mercurial repositories
Summary: Ref T12961. Fixes T4416. Currently, for observed Mercurial repositories, we build a working copy with `pull -u` (for "update"). This should be unnecessary, and we don't do it for hosted Mercurial repositories. We also stopped doing it years ago for Git repositories. We also don't clone Mercurial repositories with a working copy. It's possible something has slipped through the cracks here so I'll hold this until after the release cut, but I believe there are no actual technical blockers here. Test Plan: - Observed a public Mercurial repository on Bitbucket. - Let it import. - Browsed commits, branches, file content, etc., without any apparent issues. Reviewers: chad Reviewed By: chad Subscribers: cspeckmim Maniphest Tasks: T12961, T4416 Differential Revision: https://secure.phabricator.com/D18390
This commit is contained in:
parent
794e185bf9
commit
2c150076b0
1 changed files with 1 additions and 1 deletions
|
@ -529,7 +529,7 @@ final class PhabricatorRepositoryPullEngine
|
|||
|
||||
// This is a local command, but needs credentials.
|
||||
$remote = $repository->getRemoteURIEnvelope();
|
||||
$future = $repository->getRemoteCommandFuture('pull -u -- %P', $remote);
|
||||
$future = $repository->getRemoteCommandFuture('pull -- %P', $remote);
|
||||
$future->setCWD($path);
|
||||
|
||||
try {
|
||||
|
|
Loading…
Reference in a new issue