In T15006#279, @avivey wrote:
- Emails have a bunch of X-Phabricator-* headers, for configuring rules in mail clients.
I don't know how often they are used (GMail doesn't support rules based on headers), but we may want to allow installs to keep it as Phabricator for compatibility.
- Queries
- All Stories
- Search
- Advanced Search
- Transactions
- Transaction Logs
Feed Advanced Search
Advanced Search
Advanced Search
Jul 7 2021
Jul 7 2021
Jul 6 2021
Jul 6 2021
Added related task T15006 since it could likely serve as a reference for this one... Please undo or stop me if I'm overstepping boundaries
dcog added a parent task for T15026: Create a migration guide to move from Phabricator to Phorge: T15006: Re-brand Phorge.
dcog added a subtask for T15006: Re-brand Phorge: T15026: Create a migration guide to move from Phabricator to Phorge.
In T15011#370, @willson556 wrote:I actually started on a VSCode Devcontainer based solution on my GitHub: https://github.com/willson556/phorge-devcontainer
I want to also mention on this topic... Using a pre-packaged VirtualBox image can be a straightforward distribution route, with a drawback being filesize... Perhaps Torrents could be a neat way alternative to distribute something like that, though there would be a few options including sponsored mirrors, etc... VirtualBox is a common Vagrant provider, so oftentimes it is a prerequisite anyway...
We should consider a Vagrantfile
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?
Content licensed under Creative Commons Attribution-ShareAlike 4.0 (CC-BY-SA) unless otherwise noted; code licensed under Apache 2.0 or other open source licenses. · CC BY-SA 4.0 · Apache 2.0