I think I just imagined replacing the (default) query from "tasks tagged with project X" to "tasks tagged with project X or any subproject of X".

In T15249#6218, @ton wrote:

I don't mind if someone points me at the right place in code so I can try my luck with writing PHP.

As an alternative to using the "upload raw diff" option, see also https://secure.phabricator.com/T5000, and in specific the "magic ref" stuff in T15096#2329 and https://secure.phabricator.com/D9599.

At least using svn 1.13.0, adding --show-inherited-props to the command doesn't print an error and exits with status 0 from the propget command, but I'm not sure what it actually does.

@valerio.bozzolan - marking all bugs in Arcanist as subtasks of this task is not helpful. This task is about discussing users not being happy about arcanist; No specific bug or specific broken use-case is actually relevant to having users not want to use it, because in almost all cases users either refuse to even try it (so they are not effected the bug).
Bugs that are found and are causing any discomfort are fixed.

adding a " full screen" button in the mobile view might just solve this.

• catch Throwable

Added a test-script to check all possible inputs. It's not run automatically, because this isn't part of the main code.

add tests and keep simplest code

In D25115#3613, @valerio.bozzolan wrote:

Honestly I cannot test since - in both cases - in my local installation that section is just empty:

Any tip?

Since the bug you found was major, and my tests didn't catch it, I'm going to do another round of more in-depth testing for this...

Phactory [will] also want an in-brand logo.

one lint issue that escaped, otherwise good.

I've updated the description.
This isn't about colors; there's a drop-down in Project called "color", and editing sometimes changes the value of that field.

I removed the tag from some tasks that are about Workboards and not about projects.

Projects isn't archived.

I'm done cleaning up Projects for now.

Yeah, this two changes (adding a class and using it) should go together.

I'm ok with you creating a new Files tag for the Files app.

We have a really good text-search system. Just go to maniphest and search for "files", you'll get everything that's related to it.

I archived Files (archived) because there was nothing there.
If it gets traffic, we can create a relevant tag.