when working on multiple machines it may happen that a review request
only exists on one machine A and in the staging area, but not in the upstream repository.
So when working on machine B and you try to land a review that was just accepted, this does not work:
$ arc land D72 Branch "D72" does not exist in the local working copy.
To fix this I do normally the following:
$ arc patch D72
this gives you the branch ‘arcpatch-D72’.
Now you have the changes but
arc land D72 will still fail, because of the wrong branch name.
Then I simply create the expected branch name using
git branch D72.
arc land D72 succeeds.
It would be nice if “arc” could streamline this process to “just work” even if the branch does not exist yet on the local machine. As you can see, technically it is possible, just not with a single “arc land” command.
I know, another workaround is pushing the review request to a personal feature branch in the upstream repo before it was accepted, but sometimes you just forget this. Making “arc land” working as I proposed would be a huge benefit IMO.
This could also be useful for automatic landing, e.g. after passing all CI builds.