FWIW even in the case the milestones are strictly ordered, it's incredibly inconvenient to sort out a situation where you need to add one to the middle of the list - forcing the user to rename a bunch of them to get things straightened out.

In T15082#2028, @golyalpha wrote:

epriestley was very much against this idea but wikimedia's users loved it.

Do we have epristley's reasoning as to why he was against this? Might help in deciding about including this patch in Phorge.

I like your assumption of good faith! I'm a little more cynical about the thoughtfulness of Phab development, and the thoroughness of features deployed. I'll try to follow your example. :)

In D25072#2285, @valerio.bozzolan wrote:

So the goal is:

• stop other listeners: that's why I've adopted stop()
• don't prevent anything: that's why I've not called prevent()
• don't open the pop-up: that's why I've set that return;

Shit - you was really fast

fix lint error "Line Too Long"

I noticed that, if you click on whatever other link while you are editing something, the Dialog is not show, and you just can lose your work.

Thank you @dcog for this Dialog confirmation that saves my day.

I don't think the hundreds of installations that use Phorge would want to abandon the way they do their thing so drastically. That is why I suggest to think about something that helps both them and you.

rename getPageID() to getMonogram() and add few inline comments

• fix

(I haven't seen @20after4 for a while now. Also @0).

• change language and replace "status" with "isHidden"
• celerify

Thanks for your help! Much appreciated that the attention on this is being raised. :)

So, if I have understood correctly,

Let's try to exclude some things. Are you sure that the phd is executing that file - just like the frontend? It happens sometime that some people has both Phorge and Phabricator and phd runs some files and the frontend some others. Are you using CentOS or any other distribution with SELinux enabled or this kind of security restrictions? Is there any security directive set in the systemd unit of phd? I think you are doing everything just right, but thank you for clarifying what you tried.

Hi! Thanks for following up on this. :)

Definition of the custom field that is queried:

Can you share a screenshot to this fact of... true or any but not false? Thank you so much

Its basically a predefined query that is called via conduit:

Thank you for this question. At the moment I think the answers are useful. I invite people in contacting you to give you support. In the meanwhile feel free to add more comments / reopen etc.

I'm marking this as resolved since I think the answer is useful. Feel free to share more comments / reopen etc. Thank you!

Feel free to share more details even if it's closed - we can alway reopen. Thank you

Feel free to reopen when you have more details

How do you currently express your search query?

(If you go in file {F202556} and make it visible, please write a comment so we can reopen this question. Thank you!)

Thank you for this question. Feel free to reopen or make a new one!

Thank you for this question. Since you already have two positive answers, feel free to create another Question, or you can also create a Task to track down a goal.

Please change the visibility of the file F202556 since I cannot see it

In T15096#3967, @valerio.bozzolan wrote:

One thing that could help a lot for my survival, for example, is the creation of a small bot able to convert the GitHub/GitLab flow to the Phabricator flow - automagically.

So, if I have a repository mirrored to GitHub in read-only, people can just do a pull request, and their stuff is converted to an arc diff, without any intervention from the code contributor.

I only warn that I work on it, because I need it for some personal side-projects hosted in my personal Phabricator - and where I don't want to yell at contributors who send pull requests from elsewhere.

One thing that could help a lot for my survival, for example, is the creation of a small bot able to convert the GitHub/GitLab flow to the Phabricator flow - automagically.

We can also start with 2, and then migrate to 1 when we will receive boatloads of donations from GitLab haters.