as stated in https://secure.phabricator.com/book/phabricator/article/audit/, lets consider this scenario:
- Bailey notices a few minor problems with Alice’s commit. She leaves comments describing improvements and uses “Raise Concern” to send the commit back into Alice’s queue.
- Later, Alice logs into Phabricator and sees that Bailey has raised a concern (usually, Alice will also get an email). She resolves the issue somehow, maybe by making a followup commit with fixes.
- After the issues have been dealt with, she uses “Request Verification” to return the change to Bailey so Bailey can verify that the concerns have been addressed.
In other words, this is typical situation: developer makes commit -> someone spots problem and inform developer -> developer makes fix -> problem solved.
We have commit A and corresponding audit with raised concern. Developer addressed that concern and made next commit B. The fix was OK, however this commit is not linked to original audit in any way. When we mention the commit B in the audit comment, it is indeed linked, but only as a reference. We expected that the commit B will be somehow joined to the audit, or overtakes it, or something like that, so the audit can be resolved by accepting commit B.
Clearly, we miss some information how to “link” commits to audit or we do not understand the recommended audit workflow - specifically what is meant by “followup commit”.
Can anybody give some hints or explanation?