Guide to the Audit (post-push code review) tool and workflow.
Phabricator supports two code review workflows, "review" (pre-push) and "audit" (post-push). To understand the differences between the two, see User Guide: Review vs Audit.
This document summarizes the post-push "audit" workflow implemented by the creatively-named Audit tool.
Using auditing allows you to push and deploy code without waiting for code review, while still doing code review eventually. The Audit tool primarily keeps track of two things:
In the Audit tool's home screen (at /audit/) and on the homepage you can see commits and requests that require your action:
Audit requests can be triggered in a number of ways:
If you have a small team and don't need complicated trigger rules, you can set up a simple audit workflow like this:
This way, everyone will see an audit request for every commit, but it will be dismissed if anyone approves it. Effectively, this enforces the rule "every commit should have someone look at it".
Once your team gets bigger, you can refine this ruleset so that developers see only changes that are relevant to them.