Issues like this to me (see also T11433) don't really belong in everyday documentation. The main reason being if we continually add these rare or one-time incidents to the documentation, the documentation becomes watered down, difficult to read, and likely admins will miss the more important points. We already provide Maniphest and Ponder for more alternative questions about Phabricator, which Google is good about indexing, as well as our own search engine.

I'm not sure what you could do that would really prevent this, other than changing these to real files. But as you said, it's probably not worth it. As long as users are aware of it, it could prevent these issues from popping up periodically.

Closing for lack of reproduction steps, version information, etc. Please see Contributing Bug Reports and follow our guide if you need help with Phabricator.

It's not our intention to provide detailed examples for every scenario or operating system, given the tens of thousands of possible examples needed.

Also be careful that the 'Depends on:' commit message parsing is strictly additive; if you ever change patch order in any way, your dependencies will get out of whack. If you're doing this, you can modify DifferentialTransactionEditor to reset the dependencies before parsing, but this means you throw away any dependencies manually added through the web UI.