@recaptime-dev's working patches + fork for Phorge, a community fork of Phabricator. (Upstream dev and stable branches are at upstream/main and upstream/stable respectively.) hq.recaptime.dev/wiki/Phorge
phorge phabricator
1
fork

Configure Feed

Select the types of activity you want to include in your feed.

at recaptime-dev/main 53 lines 1.9 kB view raw
1@title Differential User Guide: Automated Landing 2@group userguide 3 4Configuring Phorge so you can "Land Revision" from the web UI. 5 6 7Overview 8======== 9 10IMPORTANT: This feature is a prototype and has substantial limitations. 11 12Phorge can be configured so that approved revisions may be published 13directly from the web interface. This can make publishing changes more 14convenient, particularly for open source projects where authors may not have 15commit access to the repository. This document explains the workflow and how to 16configure it. 17 18When properly configured, a {nav Land Revision} action will appear in 19Differential. This action works like `arc land` on the command line, and 20merges and publishes the revision. 21 22This feature has significant limitations: 23 24 - This feature is a prototype. 25 - This feature is only supported in Git. 26 - This feature always lands changes onto `master`. 27 - This feature does not currently provide chain of custody, and what lands 28 may be arbitrarily different than what is shown in Differential. 29 30To be landable, a revision must satisfy these requirements: 31 32 - It must belong to a repository which is tracked in Diffusion 33 (both hosted and imported repositories will work). 34 - The repository must have a **Staging Area** configured. 35 - The repository must have **Repository Automation** configured. For 36 details, see @{article:Drydock User Guide: Repository Automation}. 37 - The revision must have been created with `arc diff` and pushed to the 38 configured staging area at creation time. 39 - The user clicking the "Land Revision" button must have permission to push 40 to the repository. 41 42If these requirements are met, the {nav Land Revision} action should be 43available in the UI. 44 45 46Next Steps 47========== 48 49Continue by: 50 51 - configuring repository automation with 52 @{article:Drydock User Guide: Repository Automation}; or 53 - returning to the @{article:Differential User Guide}.