test page
1Zhttps://secure.phabricator.com/w/test_page/#derp-code/

This appears to have had a regression at some point

that's good enough for me but the UI and docs need improving. I'll try and get the docs at least when I have a minute.

Weird, don't recall that.

(See also T6297.)

You're watching #twitter.

Very confused why I received an email on this task. It says I was CCd, but... I don't see where? How did you create this task?

Object rules have the same edit policy as the corresponding object.

Thanks for the report, and for including version information.

Ok, thanks

:o yeah that works

Go to /applications/, then click this:

I'm experiencing a dumb.

Thanks for the quick turnaround. I'll see if the problem is fixed in 48 hours and let you know.

Er, rather, the policy hint is fine since that's the view policy.

Global rules can only be edited by users with "Can Manage Global Rules" permission (Applications → Herald → Configure → Can Manage Global Rules). By default, this is administrators.

Thanks for the report! This should be resolved at HEAD of master, and promote to stable in about 48 hours.

Thanks for the report! This should be fixed in HEAD of master, and will promote to stable in about 48 hours. Let us know if you're still seeing issues after updating or if you run into anything else.

The /62/ version of the URI's is something new. All the jobs we created in jenkins have been created with the /CALLSIGN/ version of the URIs. The mercurial plugin for jenkins is most likely looking for the URI property of the jenkins job and matching on that.

Thanks, those specifics are helpful.

Thanks for the report!

The problem seems still to be there.

999

Right, so I can make a parent task "Launch Product" and have subtasks of "Build Product", "Write Marketing", "Contact PR". All of these subtasks live on different workboards on different columns.

A big issue here is about terminology: Phabricator doesn't actually have a "sub-task" object; The "Create Subtask" button creates a "regular" task, that's Blocking the "parent" task.

Phabricator Tasks aren't trees, and aren't tied to an individual project or column.

D16006 is the main fix; CORGI is resolved in secret at https://meta.phacility.com/D84.

Fix for this is on meta, but the short version is that it works fine as-is.

Yeah, --force is a little weird as a name given what it actually does.

Maybe --force should be renamed to --paths then, because it's clearer?

I currently have b aliased to arc browse, so I type something like gfg TrainStation | x b.

Maybe --force could even just do that, without needing a new argument, since it already forces argument interpretation as paths? So the behavior would be:

Do you type that explicitly, or would something like find-some-files | xargs arc browse --paths ("force any arguments to be interpreted as paths") be good enough?

I don't remember where, but at some point I explicitly asked that arc browse with no arguments will not browse anything, to allow [my] workflow of find-some-files | xargs arc browse. At the time, it was suggested that it would default to arc browse . (I think it only knew about paths at the time).

Yeah sounds like they didn't grok my initial reply.