clarify how to run the command (last change promise)

Aldo I may need extra help from @waldyrious asdlol

aaand I go to bed :3

OK my friend, I've worked a lot to make it shorter... but still more dense of useful info, reducing jokes at minimum.

This is much better. A few spelling errors remain, plus two suggestions to make sentences read a little less awkward.

Dear friend @mainframe98 - I suggest to click the button Hide "Done" inlines in the top-right corner to easily do another reading

last cosmetic change on a title with extra "==="

add missing comma

implement tips, simplify (thanks)

@valerio.bozzolan: Would you like to give this a (hopefully) final review? TIA!

Yeah that makes sense, thanks!

• rebase again

Double slam-sgtm

./bin/celerity/map

I find the current iteration too difficult to read, although that may be partially caused by the mutual language barrier.

Oh, I miss-understood the problem statement. The 4096 limit is on the size of the image that we can resize from...

Maybe since "we live in interesting times" we can increase such limit indeed also, but that logic makes some sense (but terrible user experience, I agree lol)

I also thought that, but I think the current limitation (4096 x 4096) is reasonable and was introduced to avoid to scale huge things and mitigate resource exhaustion in thumb generation.

I'd expect it to just resize the image as needed....

Abandoning in favor of T15890 and D25774 per previous discussion

The solution was to take direct children project and call $child->setParentProjectPHID($my_parent_phid).

This was more tricky than expected. Basically we "just" need to call PhabricatorProjectsMembershipIndexEngineExtension method materialize() on the parent.

Finally in my Phorge I can kill these milestones \o/

OK. If you are partially mentioning nonsenses in we.phorge.it itself, you are indeed right.