Claiming this. Now that I've done this, I will take the time to document then I will close this task.

What if you upgrade a heavily modified (forked) Phabricator to the vanilla Phorge?

Follow-on task filed as T15120.

What if you upgrade a heavily modified (forked) Phabricator to the vanilla Phorge?

The following task creation policy is set:

• All users can create security tasks.
• Only members of Trusted Contributors may create non-security tasks.

@avivey no worries and you're welcome. I was afraid I was maybe in the process of making an ass out of myself…

ah, I see the error now.
yes, that's a typo - it was carried over from an earlier version of the document.
in phase 5, only node-modules should be removed, not the package files.
thank you for reporting, and sorry I was being harsh - I forgot I split this section and only looked at the primary blob of commands.

@avivey I'm not here to troll, I'm sincerely puzzled, even more by comparing T15019 to the instructions above.

@kwisatz - did you actually try to follow the instructions and ran into a problem, or are you just speculating?

Unfortunately, running npm install in a directory that does not contain a package.json file does exactly nothing.
Maybe the instructions are wrong and we're supposed to delete node_modules/ and package-lock.json but not package.json which I see actually got added in rP2258ba8535d57081582add7375c31837ac2f26f3.

I just tried it here, and it didn't require any auth. maybe something was wrong with our setup at the time?

Auto file attachments are also not working when editing a comment.

We've made it to y-combinator, so I think that counts.

Fixed and deployed.

I think we can close this now.

Why do we run npm install when we have previously deleted the package.json file from that directory?

Differentiate between metadata of different text areas using node ID. e.g., new comment text areas and text areas in the edit comment dialog.

ran celerity map again

@avivey what would be required to merge @Dylsss 's patch into phorge stable?
(This thing has been annoying our team for the past few weeks)

The aphlict instructions are confusing.
Why do we run npm install when we have previously deleted the package.json file from that directory?

Should I make a draft for the starmap privately and then publish it when done?

There is a thread to translatewiki.net about adding Phorge: https://translatewiki.net/wiki/Thread:Support/Adding_Phorge_for_translation%3F.
Wikimedia must first migrate to Phorge to add it into translatewiki.net.

In T15117#2892, @jupe wrote:

Happy to create empty pages (I somehow feel that a wiki page with a fat TODO might be marginally better than a 404 :))

There is no need to make a modern software compatible with PHP 5.x so I can agree to this change.

Happy to create empty pages (I somehow feel that a wiki page with a fat TODO might be marginally better than a 404 :))

thanks - not technically a dupe, because there's no ticket, but D25050 would fix those.

@jupe these 404 errors appears because the documentation pages linked were not yet created.

Thank you Cigaryno.

If you want to copy the Diviner doc from https://secure.phabricator.com or https://we.phorge.it, you may create documents at Diviner or Phriction and set an edit policy if needed. To disable applications you don't need, click More Applications in the homepage, click Manage and then Uninstall on applications you don't need on your instance. To migrate from Phabricator to Phorge, see this manual.

@Cigaryno Phabricator ( for now )

@SmoothPlay are you using Phabricator or Phorge as server software.

This task is mostly done so I think it should be closed as resolved.

arc liberate

Linting

Great that works perfectly thanks

There are no more Phabricator references in Diviner so I think this revision may be accepted.

In brief, Maniphest is for bug reports or feature requests and Ponder is for asking questions about Phorge.

(should also include the rHP -> /home/ stuff)

Done - deleted phabricator books.

I've updated the guide with @jeremy.norris's Aphlict instructions, and also a section about configurations we might change later.

In T15026#2840, @avivey wrote:

the Aphlict change sounds simple enough to just add to the migration guide - it's going to happen at the same time for basically everyone anyway.

Edit: Looks like this issue was raised in the PR D25006#216

In T15026#2841, @jeremy.norris wrote:

FYI, I believe I was able to create a linear history from Phacility's stable branch with the following:

Phorge:

git checkout master
git remote add phacility https://github.com/phacility/phabricator.git
git fetch phacility
git checkout -b stable_linear phacility/stable
git merge -m "(stable) Promote 2022 Week 37" origin/master

Arcanist:

git checkout master
git remote add phacility https://github.com/phacility/arcanist.git
git fetch phacility
git checkout -b stable_linear phacility/stable
git merge -m "(stable) Promote 2022 Week 37" origin/master

You can view the results on my Github here:
https://github.com/norrisjeremy/phorge/tree/stable_linear
https://github.com/norrisjeremy/arcanist/tree/stable_linear

FYI, I believe I was able to create a linear history from Phacility's stable branch with the following: