= What is Phork? = **Home Page:** http://getphorked.github.io/ Phork is a set of patches that can be applied to Phabricator (http://phabricator.org) to gain additional functionality. = Why do this? = Not everything that is built around Phabricator is accepted into upstream, either because the patches don't lie on the upstream roadmap, or the upstream maintainers are currently focused elsewhere. = What features does Phork have? = See the full article on what features are present in Phork that are not available in Phabricator. = How do I upgrade Phabricator? = Phork is a strict super-set of Phabricator. The repository is rebased continuously on top of the latest master branch from Phabricator, ensuring that upgrading Phabricator to Phork is as simple as: $ cd phabricator $ git remote rm origin $ git remote add origin git://github.com/getphorked/phabricator.git $ git pull Apply the same commands to libphutil and Arcanist, and then run `bin/storage upgrade` as you would for any other Phabricator upgrade. = What are communities? = Communities are what we call a set of patches to Phabricator. You might have a series of patches related to Phrequent, or you might have a series of patches that adds support for TFS source control. In these cases, the branches would be called community-phrequent and community-tfs. Each community is rebased off the upstream master branch, ensuring they remain independent of one another and that breaking changes in upstream will only affect a subset of the functionality that Phork provides. = What are profiles? = Not all additions to Phabricator that lie in Phork are compatible with each other. Thus there are a series of profiles that provide compatible functionality. The default profile is the master branch, all other profiles have the profile- prefix on the branch name.

= What is Phork? = **Home Page:** http://getphorked.github.io/ Phork is a set of patches that can be applied to Phabricator (http://phabricator.org) to gain additional functionality. = Why do this? = Not everything that is built around Phabricator is accepted into upstream, either because the patches don't lie on the upstream roadmap, or the upstream maintainers are currently focused elsewhere. = What features does Phork have? = See the [[phork/features|full feature list]] on what features are present in Phork that are not available in Phabricator. = How do I upgrade Phabricator? = Phork is a strict super-set of Phabricator. The repository is rebased continuously on top of the latest master branch from Phabricator, ensuring that upgrading Phabricator to Phork is as simple as: $ cd phabricator $ git remote rm origin $ git remote add origin git://github.com/getphorked/phabricator.git $ git pull Apply the same commands to libphutil and Arcanist, and then run `bin/storage upgrade` as you would for any other Phabricator upgrade. = What are communities? = Communities are what we call a set of patches to Phabricator. You might have a series of patches related to Phrequent, or you might have a series of patches that adds support for TFS source control. In these cases, the branches would be called community-phrequent and community-tfs. Each community is rebased off the upstream master branch, ensuring they remain independent of one another and that breaking changes in upstream will only affect a subset of the functionality that Phork provides. = What are profiles? = Not all additions to Phabricator that lie in Phork are compatible with each other. Thus there are a series of profiles that provide compatible functionality. The default profile is the master branch, all other profiles have the profile- prefix on the branch name.

= What is Phork? = **Home Page:** http://getphorked.github.io/ Phork is a set of patches that can be applied to Phabricator (http://phabricator.org) to gain additional functionality. = Why do this? = Not everything that is built around Phabricator is accepted into upstream, either because the patches don't lie on the upstream roadmap, or the upstream maintainers are currently focused elsewhere. = What features does Phork have? = See the [[phork/features|full articlefeature list]] on what features are present in Phork that are not available in Phabricator. = How do I upgrade Phabricator? = Phork is a strict super-set of Phabricator. The repository is rebased continuously on top of the latest master branch from Phabricator, ensuring that upgrading Phabricator to Phork is as simple as: $ cd phabricator $ git remote rm origin $ git remote add origin git://github.com/getphorked/phabricator.git $ git pull Apply the same commands to libphutil and Arcanist, and then run `bin/storage upgrade` as you would for any other Phabricator upgrade. = What are communities? = Communities are what we call a set of patches to Phabricator. You might have a series of patches related to Phrequent, or you might have a series of patches that adds support for TFS source control. In these cases, the branches would be called community-phrequent and community-tfs. Each community is rebased off the upstream master branch, ensuring they remain independent of one another and that breaking changes in upstream will only affect a subset of the functionality that Phork provides. = What are profiles? = Not all additions to Phabricator that lie in Phork are compatible with each other. Thus there are a series of profiles that provide compatible functionality. The default profile is the master branch, all other profiles have the profile- prefix on the branch name.