One of my developers created a review for a change in a branch, then pushed which closed the review. The change was then merged to another branch where a conflict happened. He resolved the conflict and attempted to create another review for the merge. He got an error indicating that the revision was already closed. He should be allowed to create a new revision for his merged code.
$ arc diff --create
You have untracked files in this working copy.
Working copy: /path/to/repo/
Untracked files in working copy:
path/to/file
Since you don't have '.gitignore' rules for these files and have not listed
them in '.git/info/exclude', you may have forgotten to 'git add' them to
your
commit.
Do you want to amend this file to the commit? [y/N] N
You have a saved revision message in '.git/arc/create-message'.
Message begins:
Fixing merge conflict.
You can use this message, or discard it.
Do you want to use this message? [Y/n] Y
Linting...
No lint engine configured for this project.
Running unit tests...
No unit test engine is configured for this project.
Exception
ERR_CLOSED: This revision has already been closed.
(Run with --trace for a full exception trace.)