@avivey I'm not here to troll, I'm sincerely puzzled, even more by comparing T15019 to the instructions above.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
All Stories
Sep 20 2022
@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?
Sep 19 2022
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.
Sep 18 2022
ran celerity map again
The aphlict instructions are confusing.
Why do we run npm install when we have previously deleted the package.json file from that directory?
Sep 17 2022
Should I make a draft for the starmap privately and then publish it when done?
Sep 16 2022
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.
Sep 15 2022
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.
Sep 14 2022
This task is mostly done so I think it should be closed as resolved.
Sep 12 2022
arc liberate
Linting
Great that works perfectly thanks
Sep 10 2022
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.
Sep 9 2022
(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/masterArcanist:
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/masterYou can view the results on my Github here:
https://github.com/norrisjeremy/phorge/tree/stable_linear
https://github.com/norrisjeremy/arcanist/tree/stable_linear
Sep 8 2022
FYI, I believe I was able to create a linear history from Phacility's stable branch with the following:
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.
Since the user base is probably pretty small for stable in Phorge, I wonder if it could just be deleted altogether? And then create a new stable in Phorge, that is based directly off of Phabricator's stable, then perform a squash merge or cherry-pick of Phorge master into the new Phorge stable?
I'm not 100% certain how Evan handled promotions of Phabricator master into stable (if he just cherry-picked, or he used squash merges or something different altogether)?
re: stable, I'm not sure how the commits actually relate between the now 4 branches.
I considered adding git reset --hard for stable, but I was afraid users will lose local changes.
So you have a suggestion on how to fix the guide for stable?
In T15046#2789, @Matthew wrote:
need to create a username/password passphrase credential with creds for a GitHub account that has write access to the GitHub repos, and set it in the diffusion uris.
I was hoping that wouldn't be the case. I'll create a credential against my account, since it's currently impossible to create GitHub account keys against an orginization.
The master branch in Phorge is linear with respect to Phabricator's master branch, but it looks like the stable branch in Phorge was created by branching it directly from the tip of Phorge's master, instead of using Phabricator's stable branch as the basis.
It looks to me that Phabricator was cherry-picking their master to their stable, so the changeset history wasn't directly linear with their master (hopefully that makes sense?).
So the directions from the migration guide end up creating a huge local merge commit when followed if you were tracking Phabricator's stable branch.
In T15026#2812, @jeremy.norris wrote:FYI, the guide for migration doesn't seem to work quite smoothly for folks that were tracking the stable branch for Phabricator, because the new stable branch in Phorge does not have a linear changeset history to the old stable branch in Phabricator: if you follow the directions, you end up with a locally divergent stable branch that will contain a local merge commit.
Is there a reason the stable branch in Phorge wasn't created based upon the changeset history of the stable branch in Phabricator, in order to avoid this from happening?Also, on a separate note, the changes from T15019 cause a conflict when issuing the git pull command:
error: The following untracked working tree files would be overwritten by merge: support/aphlict/server/package-lock.json support/aphlict/server/package.json Please move or remove them before you merge. AbortingShould some notes be added to the migration guide on how to best deal with this as well?
Oh actually they do work now - never mind
The GitHub mirrors still don’t work yet, those reps are empty currently.