Complete steps which allow someone else who does not have access to your environment to reproduce the bug.
I am now prompted “Land these changes?” and have to confirm before the changes will land. In older versions of arcanist,
arc land would simply land the diff.
$ arc land (git log --format="%h" master.. | tail -1) && git fetch origin master:master && git rebase master STRATEGY Merging with "squash" strategy, the default strategy. ONTO REMOTE Landing onto remote "origin", the default remote under Git. ONTO TARGET Landing onto target "master", the default target under Git. INTO REMOTE Will merge into remote "origin" by default, because this is the remote the change is landing onto. INTO TARGET Will merge into target "master" by default, because this is the "onto" target. FETCH Fetching "master" from remote "origin"... $ git fetch --no-tags --quiet -- origin master INTO COMMIT Preparing merge into "master" from remote "origin", at commit "bb2dfd7ef05a". LANDING These changes will land: * D7201 Move user profile from redux to react context c2b93b419917 Move user profile from redux to react context >>> Land these changes? [y/N/?] y
Output from Config > Version Information or
$ arc version arcanist 33dfa859d8e68a66559c15c78cea4da19204653b (12 Jun 2020)