One possibility here is to reopen a Maniphest task if a "fixes" commit is reverted. I'm not sure whether this behavior is desirable.

There is no relevant "explain why" link because there is no transaction for someone added a commit: rPPfd5a74ad3fa1 on D19839 or someone added a differential revision: D19839 on rPPfd5a74ad3fa1.

In T7447#110475, @scohen wrote:

I don't know @epriestley, I found it really confusing to have my comment on a different line entirely.

Personally, I felt that (at least in the case of my screenshot) it would be better to push the entire tag to the second line.

When I first read the title of this ticket, I thought that you were going to add gamification.

Could badges be used for policies? For example, Blessed Committers could be replaced with a badge potentially. This would (at least partially) solve T5602.

#1 gets my vote.

Here's an updated profile, this time from linting rP:

It looks like the most significant function is AASTNode::getTokens.

Here is a better profile (F379444), see https://secure.phabricator.com/xhprof/profile/PHID-FILE-k7tcfv6t7e7o3itxfwns/.

Can you remind me why we lint by linter instead of by path? As in, we lint all paths for a given linter before moving to the next linter.

This has magically fixed itself.

you sir, are awesome.

Would this task be available for paid prioritization?

Weird, the notifications did come through on my phone.

In T7880#108099, @epriestley wrote:

Do you have the durable chat column open?

Hmm, looking in the network tab in Chrome and I can't actually see a websocket connection.

Could be related to this?

In T7880#108096, @joshuaspence wrote:

Actually, our firewall might be blocking port 22280... that's one of the reasons that I run Aphlict over port 443.

Actually, our firewall might be blocking port 22280... that's one of the reasons that I run Aphlict over port 443.

In T7880#108085, @chad wrote:

I have no idea what "this morning" means time wise in NZ to CA, haha

In T7830#107243, @chad wrote:

Issues with Workboards and Conpherence were resolved earlier this week.

I can't remember exactly what the issue was, but there's something funky with work boards and setup issues as well.

T7045 is maybe relevant here.

I really wish that we could fix this as it drives me insane to the point that I try not to send inbound emails to Phabricator. I don't, however, have any ideas on how to tackle this. Specifically, I don't see how we can differentiate automatic line breaks inserted by Gmail from intentional line breaks inserted by the user.