Yeah, what Chad said. Basically, A “Revision” is the base unit of review in our workflows (Which translates to a single commit); If you want each commit to be reviewed separately, then you should create a separate Revision from each one (
arc diff HEAD~).
The guiding principle should be something like “Does this change makes sense on its own?” or maybe “year from now, when someone a blames a bug to a commit - will that commit/revision useful?”.
You can create a set of dependent revisions, it’s just a little more work. When I need to do that, I usually first squash the changes to one-commit-per-review, and then run something like
git rebase -x arc diff HEAD~ or something do that extent. I think the biggest set I’ve ever had was maybe 4 revisions deep though.