@chad this isn't an everyone-everywhere change. Here the expectation, at least for me, is that the natural sort edit should follow the workboard edit policy, not the task edit policy.

T6502 is related except that even if that were to be permissive it wouldn't be possible to edit the sort since the underlying task lacks edit capability. That said, it is the ticket I was thinking of.

to be clear: the #Twitter project was already added to the project. The expectation was that changing the *natural* state (as opposed to the priority state) would be allowed.

for future people: git seems to ignore ~/.curlrc but you can pass a proxy using -chttp.proxy or using the https_proxy variable.

One additional usecase for subprojects: it would be very nice to be able to move subprojects between different parents. In particular lets say we have
team1 > productA
team1> productB
team2> productC
and as a result of a re-org or some other influence productA moved to team2. To do the move now we'd have to create a new project, reconfigure it (cloning the workboard), and mass change the labels (remembering where in the workboard every task is).

T731, T1279, and T10574 are all likely related.

In T10621#165969, @epriestley wrote:

How do you imagine Phabricator learning about the existence of new external groups? Just polling a list of every group in LDAP every hour or whatever?

This would be fully solved with T8629 so I'm just going to close it :/

arc diff --plan-changes ?

oh, I'm just braindead: I skipped over the nav portion entirely since it wasn't the obvious thing I wanted.

I wanted to use it for de-emphasis (like you're aside) and for inside of tables for various things. I was also trying to use it for a small "edit this panel" link like the other task but the href on the button is cooler.

oh, cool. That should be documented, but is exactly what I wanted.

this task might more generally: support inline remarkup in link names. I havn't tried to make image, bold, or other interesting links.

for anyone else that runs into this in the future: http://www.gossamer-threads.com/lists/wiki/mediawiki-cvs/626638

In T10623#166012, @epriestley wrote:

We have a large, and growing, set of teams that would like to get CCed whenever a review is created in a repository they work in.

Would something like adding "Watch Repository", like "Watch Project", so users could get CC'd on every commit and revision for a given repository possibly be a better solution for this?

Understood. Thanks for the information.

In T10628#166000, @richardvanvelzen wrote:

FWIW, I've pretty much never looked at "Open Revisions Affecting These Files", and only look at "Local Commits" to check if the parent commit is already pushed.