- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Advanced Search
Aug 12 2020
To be completely clear: I'm not going to accept any features upstream which zero customers are interested in. It doesn't matter if they're simple or complicated. If no customers want it, it isn't coming upstream.
Aug 11 2020
Adding overflow-wrap: anywhere appears to fix this without breaking anything.
There's currently no customer interest in worktree support. The use cases in T9924 seem flimsy to me so I don't currently plan to support worktrees in the absence of customer interest. See also ArcanistGitWorkingCopy.
PHI1816 would also like dimensional coverage: coverage by language; coverage by team/owner. This is perhaps worth considering in how coverage is aggregated.
Aug 10 2020
Aug 8 2020
Aug 5 2020
With newer inline comment functionality there is no ability to create submitted inline comments for bots or via API directly.
I'm not aware of any current customer use cases for this behavior. I'm open to restoring it if customers are actually using it, but would like to make sure the API is fully supporting whatever the need is.
Aug 2 2020
Jul 30 2020
See PHI1833.
Jul 28 2020
Jul 27 2020
Jul 25 2020
Jul 24 2020
I reverted this in D21429, since it also makes these sequences select with a single click.
In D21426, I removed phd.trace and phd.verbose.
Jul 23 2020
- Include "obsolete config" setup checks.
- Use "$caught", not "$ex", to make the code less fragile.
- Add "ExecFuture->hasPID()" to simplify reading PID information.
The call sequence here is approximately: