The Phabricator system is part of Engineering Operations' larger [[EngineeringProductivity/Projects/Conduit|Conduit]] project to provide better automation, tracking, and visualization of the pipeline from initial patch submission through to landing in release branches. The Conduit [[EngineeringProductivity/Projects/Conduit/RoadMap|road map]] includes the Phabricator roll-out.
= BMO Integration Documentation =
Since issue tracking and code review are tightly related, and since BMO is currently the authority User documentation for identity and authorization around both issue tracking and code review, including security and other confidential bugs and fixes, our Phabricator instance will be integrated with BMO. This integration will only be to the degree needed in order to limit customization of Phabricator, which has both maintenance and opportunity costs. == Identity == The main way to log into Phabricator will be via BMOMozilla's auth delegation. A user logging into Phabricator will be taken to BMO to log in as usual and will be redirected back to Phabricator if the login succeeds. If this instance is the first time the user has logged into Phabricator, they will be prompted to create an account. They can choose to use their BMO email address or provide a new one, which will be separately verified. New users will also be prompted to enter a separate username, unlike BMO. This username will be used by Autoland to denote reviewers when constructing the final commit message. == Links from Differential to BMO == A bug number must be entered when a patch is submitted to Phabricator. This will be stored in the revision metadata and provided in the UI as a link to the associated bug on BMO. == Links from BMO to Differential == Upon the creation of a new revision in Differential, a stub attachment, containing only the URL of the revision, will be added to the associated bug. Based available on the attachment type, BMO will automatically redirect to Differential if the attachment link is clicked. == Authorization == If a bug has one or more security groups applied to it, that is, it has restricted visibility, any Differential revisions associated with it will similarly be restricted in visibility. This will initially only apply to Firefox security groups, that is, groups with names matching ''*core[http://moz-security*''. Any revision associated with a bug restricted via other groups, e.gconduit. infra, will be visible only to the author and adminsreadthedocs. We can add proper support for such groups on request. == Review flags == For simplicity, and since Differential's review system does not map cleanly to BMO's review flags, r+ flags, and only r+ flags, will be set on the stub attachment associated with a Differential revision when a Phabricator user performs an "Accept Revision" action. The flag will be removed if the user later issues a "Request Changes" or a "Resign as Reviewer" action. Similarly, all r+ flags will be removed if the author selects any of the "Plan Changes", "Request Review", or "Abandon Revision" actions. In the last case, io/en/latest/ Read the stub attachment will also be obsoletedDocs].
= FAQ =
