|Open||None||T15023 Create Phorge, a fork of Phabricator|
|Open||None||T15006 Re-brand Phorge|
|Open||None||T15026 Create a migration guide to move from Phabricator to Phorge|
- Mentioned Here
- T15046: Add GitHub mirrors for repos
D25004: Update .gitignore to account for package-lock.json
D25006: Add package.json for aphlict
T15013: Better handling of node/npm installation for Aphlict
T15014: Develop a Phorge Release Process
T15016: Update default storage namespace
T15006: Re-brand Phorge
For projects that were tracking upstream previously and able to merge, would this not be a matter of a Git config update to add or swap remotes then merge?
Or what are some initial thoughts on this process?
Thanks for creating this. I think there have been some notes in comments that mention having to make several updates
- T15016: Update default storage namespace
- T15013: Better handling of node/npm installation for Aphlict, more comments in D25004, D25006
Also there might need to be some coordination with T15014: Develop a Phorge Release Process, for the first go at least
My company are currently Phabricator users and have been watching the Phorge developments with interest in the last few months. It's been great to see the project taking shape!
We were wondering if anyone can answer: are any migrations from Phabricator to Phorge dependent on https://we.phorge.it/T15006? Is the eventual idea that Phorge will be put on GitHub, and is the branding ticket a blocker for that?