I changed everything branded Phabricator in th 10k files in my fork to Phorge and applied this change to filenames.

Another example of broken dark theme

https://we.phorge.it/book/phorge/article/installation_guide/

i can see a few mentions of Phabricator on the documentation, i am not sure if its because the documentation was left out, or because there are some elments in the codebase that still mention phabricator.

where is the standard installation documentation for phorge, i only see migration

There's a difference between deleting data as a Phab/Phorge admin (which is done via the bin/delete script, and prints out a massive warning about it potentially breaking stuff and generally being a bad idea), and schema migrations done as part of an upgrade, which would happily delete data without a second thought.

In T15126#3165, @Cigaryno wrote:

In T15126#3158, @avivey wrote:

can we keep the actual deletion as optional for a very long time/forever, and at the same time not create the database for new installs?
that will allow installs to backup/export their logs even if they miss the deprecation warning.

No, we should basically follow the two parts per @Matthew.

Also, this is fairly similar to T15082. Having Epics would probably also resolve that.

I feel like the idea behind milestones being strictly ordered is from the viewpoint that milestones are sequential "events" that happen in development one after another in a given order.

Do you talk about the DNS_PROB_STARTED error?

In D25055#1786, @Cigaryno wrote:

Could you do this:

• Replace the Phabricator logo with the Phorge logo.
• Replace the G+ like Google logo with the current Google logo that was used since 2015.

Optional: Replace the Facebook logo with the new one that has a different blue.

LGTM, we may also upstream more Wikimedia patches, per T15081: Figure out if there are patches from Wikimedia's fork that are desirable to upstream in Phorge.

Could you do this:

• Replace the Phabricator logo with the Phorge logo.
• Replace the G+ like Google logo with the current Google logo that was used since 2015.

Optional: Replace the Facebook logo with the new one that has a different blue.

In T15126#3158, @avivey wrote:

can we keep the actual deletion as optional for a very long time/forever, and at the same time not create the database for new installs?
that will allow installs to backup/export their logs even if they miss the deprecation warning.

I setup a cron that makes a bunch of DNS queries for different records within the phorge.it zone from all the authoritative nameservers for the zone (see T15080#1985).

Just resurfaced today (now).

The original discussion in T12144 is kinda convincing to me, although it's mostly convinces me that the term "milestone" doesn't match these objects.

can we keep the actual deletion as optional for a very long time/forever, and at the same time not create the database for new installs?
that will allow installs to backup/export their logs even if they miss the deprecation warning.

I think this should be done in two parts:

LGTM

I'm unable to reproduce this issue, after trying on multiple installs. I'm going to release this for someone else to take a try.

Looks good on my Mac. Screenshots attached.

I use Edge on Windows 11 with the browser font set to Segoe UI and it shows me that font.
The Ubuntu font is not used and looks to me terrible.

ok, I'll try. is there any expectation or format for the git message ?

also link to the updated Twitch docs about the auth API?

@k__nard: do you mind submitting the diffs as revisions using arc diff?

Looks like https://secure.phabricator.com/D21718 explicitly changed to always remove --quiet, so unless there's a new argument for it, this change is redundant.

I've ran this locally, and it looks the same to me (Chrome on Windows).

I've re-applied this patch and uploaded with arc diff, just to normalize it.

Bear with me here, because Javeline (like all js frameworks) is confusing to me.

just a small precision, when I said that I'm not sure about the return statement, I meant that it's working but I don't know if there is some need for testing for null data