Phabricator/FAQ: Difference between revisions

no edit summary
No edit summary
No edit summary
Line 94: Line 94:


Anyone using Phabricator is authoring patches, reviewing patches, and/or accessing confidential patches.  We feel MFA is a reasonable burden for these people given the importance of maintaining secure processes in the development of Firefox and other Mozilla apps.  Given that Bugzilla is coupled to Phabricator, and a lot of important discussion around bugs and solutions also happens in Bugzilla, including confidential discussions, anyone involved in the above activities on Phabricator should also have equal protections when accessing Bugzilla.
Anyone using Phabricator is authoring patches, reviewing patches, and/or accessing confidential patches.  We feel MFA is a reasonable burden for these people given the importance of maintaining secure processes in the development of Firefox and other Mozilla apps.  Given that Bugzilla is coupled to Phabricator, and a lot of important discussion around bugs and solutions also happens in Bugzilla, including confidential discussions, anyone involved in the above activities on Phabricator should also have equal protections when accessing Bugzilla.
=== My patch is too large for Phabricator; what are my options? ===
Phabricator has a limit of 32MB on patches.  If your patch exceed this size you should ''seriously'' consider splitting the patch into multiple commits (e.g. bumping versions of vendored rust crates one at a time rather an in a single commit).  Your reviewers will thank you for this - massive patches are harder to review.  Note if you use Lando to land your stack, each commit will land as part of the same push - you won't end up in a partially landed stack.


== Command-line tools: moz-phab and arc ==
== Command-line tools: moz-phab and arc ==
Confirmed users
1,201

edits