Garrrr, I am very sorry, I was locally experimenting with something else in master branch beforehand obviously, and while I did git stash that one file I created continued to exist in the tree when I branched to work on the dashboard exception - my fault.

Yeah, thad makes sense, I guess.

In D25548#17006, @valerio.bozzolan wrote:

I see "Unknown object" if the Diff repository is unset. Is that known?

• check for non-null repository in Revision
• rebase

I agree that an additional status is needed for closing when creating a task. Current statuses are not obvious. "Closed, Graduated" is good to fast decision.

Suddenly, yesterday I was also talking in one of the kanban communities and I had to tell them that Phorge is a fork of the Phabricator, and not some kind of independent thing without a background. People don't quite understand this.

I probably missed the train, so… can you add the docs for this? :-P

Sorry, doing my best trying to navigate both this site and Phabricator but it's a bit of an acquired taste thus far,

Pending that small inline, lgtm.

I was just surprised that they weren't here, considering that they are used very successfully on Wikimedia. Do you think they are not needed here?

Maybe better to expand the test plan to check user creation as well

Ah, probably after WMF disabled some applications, some crawlers started visiting these. Understood.

I pretended to be a webcrawlerLooking into our downstream error logs. Some crawlers seem very creative for reasons I do not know.

@avivey: still red flag?

How have you discovered this problem?

Probably we need some help to understand the semantic difference between these two:

I'm on latest master, and I'm still not able to try this 🤔 No errors. Just plaintext remarkup. Test case:

I see "Unknown object" if the Diff repository is unset. Is that known?

Tested before and after, I love this! Thanks!

• Run arc liberate from my clean working copy that has not ManiphestDefaultPriorityEditCapability (?)
• Minor fix indentation of a comment in PhabricatorDashboardQueryPanelType.php:81

Can reproduce. Tested. Thanks :)

Can't reproduce either - 🤷🏻‍♂️

@20after4

Instead of just putting it out there and letting it either succeed or fail based on the merits, there is a lot of bureaucracy around consensus building. Sadly it's just the way things are with a community/organization as large and as socialistic as Wikimedia has become.

I can relate to that. We hardly can change the social structure, but we can change the technical side. This is why I made Convenient Discussions, which contributed to speeding up the processes in communities where it was used. No more pain of meticulously editing wikitext to participate in discussions. Wikipedia has "wiki" in its name meaning "fast" in Hawaiian.

@avivey hi!
I cant reproduce it. Is the problem still there?

This guide is up-to-date up to 2022 Week 37.

@valerio.bozzolan hi! :) It seems to me that this proposal may scare someone away, since it feels like this guide is two years out of date :) Is that true?

It seems to me that this problem can be solved with an additional setting that turns this functionality on or off.