Page MenuHomePhabricator

Allow `arc diff` to run the main interactive workflow noninteractively
Closed, InvalidPublic

Description

Though we intentionally disable piped usage (see T445) arc commands, it would be better if we can optionally allow it. For example, we can config this via .arcconfig.

Event Timeline

donghang.guo raised the priority of this task from to Needs Triage.
donghang.guo updated the task description. (Show Details)
donghang.guo added a project: libphutil.
donghang.guo added a subscriber: donghang.guo.

From IRC, it sounds like the use case is that some script runs arc diff with no human interaction. arc diff is primarily intended to be an interactive tool, so I'd like to understand the use case in more detail. Adding a flag to make arc automatically choose the default for all prompts is almost certainly not acceptable in the upstream, because it's a bizarre, off-label use case.

  • What kind of process is creating these diffs, and why?
  • Why can't it use arc diff --raw?
  • Why can't it use the differential.createrawdiff Conduit method?
  • Why can't it adjust the environment in such a way that it avoids prompts?
epriestley renamed this task from Optionally allow piped arc command to Allow `arc diff` to run the main interactive workflow noninteractively.Apr 29 2014, 9:12 PM
epriestley edited projects, added Arcanist; removed libphutil.
epriestley triaged this task as Wishlist priority.Apr 30 2014, 2:14 AM
epriestley claimed this task.

This feature request doesn't have a use case, which we now require. See Contributing Feature Requests and Describing Root Problems.