From 2c150076b00f73918d6b3c86dc28e424317fc826 Mon Sep 17 00:00:00 2001 From: epriestley Date: Thu, 10 Aug 2017 17:22:32 -0700 Subject: [PATCH] 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 --- .../repository/engine/PhabricatorRepositoryPullEngine.php | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/src/applications/repository/engine/PhabricatorRepositoryPullEngine.php b/src/applications/repository/engine/PhabricatorRepositoryPullEngine.php index 32e99e619d..10eddd38d4 100644 --- a/src/applications/repository/engine/PhabricatorRepositoryPullEngine.php +++ b/src/applications/repository/engine/PhabricatorRepositoryPullEngine.php @@ -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 {