@kwisatz I'll try to review the diff this week, and that will probably get to master/stable soon...

As in E14, this is really important for protecting us and contributors.

In T15026#3074, @jeremy.norris wrote:

Wouldn't it just be easier for users if the current Phacility/stable was merged into Phorge/stable, thus avoiding the need to issue git reset --hard?

In T15026#3073, @avivey wrote:

we've decided to add git reset --hard to the instructions to avoid the merges and simplify the stable issue, avoiding the merge from multiple branches.

we've decided to add git reset --hard to the instructions to avoid the merges and simplify the stable issue, avoiding the merge from multiple branches.

In T15026#3071, @jeremy.norris wrote:

Are there plans to merge the latest Phacility/stable branch into Phorge/stable branch in order to facilitate upgrades without having local merge commits being created?

Are there plans to merge the latest Phacility/stable branch into Phorge/stable branch in order to facilitate upgrades without having local merge commits being created?

release_process has been updated.

@Leon95 I encountered a merge conflict when attempting to land these changes. Could you please take a look and try to fix and land them yourself? If you need help, feel free to ping me.

I can agree to make a legalpad that is similar to the Phacility one.

I'm actually gonna close this as Resolved - we can always reopen, or refer back to this, if the issue resurfaces.

Nothing new since last time I commented here.

Thank you for your work on this, Dan!

I'll go over this to see if there's anything left to do.

@golyalpha Are you still having this issue?

Boldly closing, as L1 exists and is available to sign.

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 :))