Good by warning 😢

Gotcha. Probably this is generating the attachment transactions but should be "ignored on no effects":

This feature is not complete also for Conpherence AFAIK

Let's visually mark this to attract people.

I've carefully read the diff :) Thanks

Totally agree. Thanks for any edit in the stub.

Have you digged Internet Archive to fix this? :)

Go pohrge!

Unrelated note, but interestingly the contributor agreement chooser (https://contributoragreements.org/) is broken. I've already sent an email to their support.

I see that it depends on a NodeJS external script (server-side).

Interesting, I agree. Note that also #bbb is valid but I see that 6 is minimum characters.

I'm also unsure and I would agree if somebody suggests to omit the Diviner page. Relevant discussion also from @avivey

It's the anniversary of this super-important killer feature 💌

I tried to understand the situation. Thanks.

It would be a pleasure to receive a patch from you :) The file should be this one:

Passed a week. Nobody commented. I blindly trust you in this field :3 Approve.

Premising that I've already accepted I noticed also this minor possible thing:

Lovely thanks :)

Again, non-blocking opinion:

Additional non-blocking thing:

First of all, I tested this, and this is super-lovely, really better than I thought, I love this. Thanks.

(Just to clarify, and sorry if late comment again - I was proposing to avoid to add buttons, and simply auto-select and auto-copy the input text the first time it receives a click. Bonus: with "copied" message feedback - I have untested this sorry)

I've successfully updated our Phabricator instance to Phorge today. After paying very careful attention to everything it went smoothly without any issues. Glad that this project has not died. Phabricator grew on me as well.

Sorry for my late comment

I've better triaged my root problem.

So maybe this is just a matter of parsing that commit part "Depends-on:" since everything else seem already implemented to me. Partially related quiz in T15738

@sirocyl Does this fix your issue? if yes, I can help in landing

My friend, I think you are affected by this change, and this applies to whatever PHP version

I super-like the result of this in /project/manage/1/, so approved.

(@speck red light)

Whops, forgot to approve this. Sorry! And thanks.

TRUST ME - YOU DON'T WANT TO LISTEN MY ENGLISH :D :D

Thanks for all the tips <3 <3

Thanks for this! BTW you are now in the family of Trusted Contributors - feel free to escalate as a Task under Bug Reports at least I think and maybe Remarkup I think. (You can do this with a manual copy-paste and we can close this as obsolete)

OK. Then we can add a Task about how to easily configure robot changes without forking, in case.

Probably, something should "Attach" these files by default to that Diff, during the upload phase.

A workaround is to make all files as "Public". I fixed for example the diff D25079: Trigger: Add Sound "Coin" by setting the audio file F1271256 as public.

What a lovely day to run a git rebase master to shine

Partially related, from the mentioned search it's easy to recognize closed Tasks, but Users are not greyed out when Disabled.

This basically works

Another thing: deletion of transactions. If by some misfortune they're around, they mess up during certain things, like T15125.

Believe me or not but I've spent 15 intense minutes to use my big eyes to check all 571 files to catch whatever line that had not the very same class name A/B.

Should we deprecate these first, before complete removal? (if easy)

I was able to recover the layout in PNG at least. Imagine this 3''x2''. Here:

I'M REALLY SORRY FOR WHAT YOU ARE GOING TO SEE - I'M NOT A DESIGNER

Sorry for my ping-pong. Thanks again for this question. I see you resolved. Feel free to flag as resolved.