Confirmed users
1,198
edits
(Link to the doc) |
No edit summary |
||
Line 7: | Line 7: | ||
== Phabricator == | == Phabricator == | ||
=== Why is my Phabricator revision showing up as "secure" or "in draft"? | |||
All revisions on Phabricator are initially non-public; when Bugzilla sees a new revision it checks the visibility of the bug and will update the revision to match: revisions referencing public bugs will be made public, and non-public bugs result in the BMO security group and CC list being mapped to the revision's policies. These are kept in sync as the bug changes. | |||
There may be a short delay after submission before the revision is visible to other users. | |||
=== Can I use Phabricator for patches to security bugs? === | === Can I use Phabricator for patches to security bugs? === | ||
Yes. Only people who | Yes. Only people who can see the Bugzilla bug will be able to see your revision. | ||
The visibility of the Phabricator revision is kept in sync with visibility changes to the bug. For example CC'ing someone to the bug will allow them to view the revision in Phabricator. | |||
=== When I clicking the Phabricator “Log In or Register” button, why is a new tab is opened with the exception ‘Unhandled Exception(“AphrontMalformedRequestException”) Your browser did not submit a “phcid” cookie with client state information in the request’ === | === When I clicking the Phabricator “Log In or Register” button, why is a new tab is opened with the exception ‘Unhandled Exception(“AphrontMalformedRequestException”) Your browser did not submit a “phcid” cookie with client state information in the request’ === |