This again broke our arc workflow. I'll look if it is needed though it would be nice to get a revert.

Is there any particular reason why we are locking these down all of a sudden? It seems like if they stay open then it is on us to to track you, which is a lot easier as we have all the info as to what our code does :D

FWIW, this is what broke / why we override:

public function getRepositoryAPI() {
$repository_api = parent::getRepositoryAPI();
if (!($repository_api instanceof ArcanistGitAPI) &&
    !($repository_api instanceof ArcanistMercurialAPI)) {
  throw new ArcanistUsageException(
    'arc cleanup-features is only supported under Git and Mercurial.');
}
return $repository_api;

In D7959#15, @LegNeato wrote:

FWIW, this is what broke / why we override:

public function getRepositoryAPI() {
$repository_api = parent::getRepositoryAPI();
if (!($repository_api instanceof ArcanistGitAPI) &&
    !($repository_api instanceof ArcanistMercurialAPI)) {
  throw new ArcanistUsageException(
    'arc cleanup-features is only supported under Git and Mercurial.');
}
return $repository_api;

There's a much easier way to do that:

protected function getSupportedRevisionControlSystems() {
  return array('git', 'hg');
}