- User Since
- Feb 20 2011, 8:41 PM (425 w, 6 d)
Fri, Apr 19
Thu, Apr 18
Wed, Apr 17
we can cache datasets by chart key very near the display layer
That screenshot produces quite the intense optical effect. I thought I was looking at moiré effect from a cellphone camera.
A half-step might be to just silence "added a commit to" in all cases?
All the same underlying action:
I feel kinda similarly about getting a flurry of "added commit to TXXX" notifications that fire in addition to the "bob closed DXXX" notifications. We don't have the infrastructure to say stuff like "only hide this notification if the same action already generated a separate notification of type foo, do we?
I guess it's not worth cleaning this up and removing the class + DB rows since it's just a no-op now and shouldn't bother anyone.
Fri, Apr 12
Thu, Apr 11
Oh whoops, I was editing the PhabricatorAuthProvidersGuidanceEngineExtension in rSERVICES.
I confess to skimming this because it's mostly code shuffling and also includes a convincing unit test.
Wed, Apr 10
Yeah, I mean, the reporter's not wrong...
ok this time i got it
Change rule to unconditionally add projects in transaction and let the editor figure it out.
Broadly, it's not clear to me that any of these rules are actually good/useful/worth building.