Page MenuHomePhabricator

Update the "WorkingCopy" API and create a fallback "Filesystem" working copy
ClosedPublic

Authored by epriestley on Apr 8 2020, 3:35 PM.
Tags
None
Referenced Files
F13267240: D21070.id.diff
Wed, May 29, 3:03 AM
F13262497: D21070.diff
Mon, May 27, 2:11 AM
F13259559: D21070.id50199.diff
Sun, May 26, 10:07 PM
F13245597: D21070.diff
Thu, May 23, 6:07 AM
F13239105: D21070.id50195.diff
Wed, May 22, 12:11 AM
F13223669: D21070.diff
Sun, May 19, 4:46 AM
F13205689: D21070.diff
Wed, May 15, 2:17 AM
F13189692: D21070.diff
Sat, May 11, 6:18 AM
Subscribers
None

Details

Summary

Ref T11968.

  • Allow "WorkingCopy" objects to maintain an API object and update callers ("get...()" instead of "new...()").
  • Always generate a WorkingCopy object and a RepositoryAPI object.

Currently, code has to look like this:

$working_copy = ...
if ($working_copy) {
  $repository_api = ...
  if ($repository_api [instanceof ... ]) {

This is clunky. There's also no reason some "arc" commands can't run outside a VCS working directory without special-casing how they interact with the filesystem.

Conceptually, model the filesystem as a trivial VCS (which stores exactly one commit, always amends onto it, and discards history). Provide a trivial WorkingCopy and API for it.

(This change isn't terribly interesting on its own, but chips away at landing the new Hardpoint infrastructure.)

Test Plan

Ran arc version, arc upgrade.

Diff Detail

Repository
rARC Arcanist
Lint
Lint Not Applicable
Unit
Tests Not Applicable