Change Details

**Changes and Compatibility Breaks** - `arc branch` is now `arc branches`. This read-only workflow shows branches in the working copy. It shows branches in every VCS (previously, it showed bookmarks in Mercurial). - `arc bookmark` is now `arc bookmarks`. This read-only workflow shows bookmarks in the working copy. It shows bookmarks in every VCS (previously, it showed branches in Git). - `arc feature`, and the write/checkout modes of `arc branch` and `arc bookmark`, are now `arc work` ("begin or resume work"). These changes are aimed at simplifying these commands, particularly in Mercurial. See T2928. Previously, it was fairly unpredictable that that `arc branch` showed bookmarks, and that `arc branch X` allowed you to //create// a bookmark, and that there were several different ways to accomplish the same goals, and that `arc bookmark X` //created a **branch**// in Git, which doesn't even have a concept of bookmarks. After these changes, exactly one command is used to accomplish each task regardless of the VCS. | Task | VCS | Old Command | New Command | |---|---|---|---| | Show branches. | git | `arc branch` or `arc bookmark` | `arc branches` | | | hg | Not Supported | `arc branches` | | Show bookmarks. | git | N/A | N/A | | | hg | `arc bookmark` or `arc branch` | `arc bookmarks` | | Work on a change. | git | `arc feature X` or `arc branch X` or `arc bookmark X` | `arc work X` | | | hg | `arc feature X` or `arc branch X` or `arc bookmark X` | `arc work X` Because `arc` automatically corrects the spelling of commands, `arc branch` and `arc bookmark` will still technically work. You can also use `arc alias` to redefine these if you've developed muscle memory for the old commands. - The `arc.feature.start.default` configuration option has been removed. Specifying a startpoint is still supported (with `arc work --start Y`). You can use `arc alias` to define a convenient alias if you'd like a command which always starts from a particular branch. I don't currently plan to restore a configuration option for this, since this isn't a behavior that impacts other people working on a project and the default behavior (branching from the current state) is generally a desirable one.

**Changes and Compatibility Breaks** - `arc branch` is now `arc branches`. This read-only workflow shows branches in the working copy. It shows branches in every VCS (previously, it showed bookmarks in Mercurial). - `arc bookmark` is now `arc bookmarks`. This read-only workflow shows bookmarks in the working copy. It shows bookmarks in every VCS (previously, it showed branches in Git). - `arc feature`, and the write/checkout modes of `arc branch` and `arc bookmark`, are now `arc work` ("begin or resume work"). These changes are aimed at simplifying these commands, particularly in Mercurial. See T2928. Previously, it was fairly unpredictable that that `arc branch` showed bookmarks, and that `arc branch X` allowed you to //create// a bookmark, and that there were several different ways to accomplish the same goals, and that `arc bookmark X` //created a **branch**// in Git, which doesn't even have a concept of bookmarks. After these changes, exactly one command is used to accomplish each task regardless of the VCS. | Task | VCS | Old Command | New Command | |---|---|---|---| | Show branches. | git | `arc branch` or `arc bookmark` | `arc branches` | | | hg | Not Supported | `arc branches` | | Show bookmarks. | git | N/A | N/A | | | hg | `arc bookmark` or `arc branch` | `arc bookmarks` | | Work on a change. | git | `arc feature X` or `arc branch X` or `arc bookmark X` | `arc work X` | | | hg | `arc feature X` or `arc branch X` or `arc bookmark X` | `arc work X` Because `arc` automatically corrects the spelling of commands and accepts unique prefixes of commands as short variations, `arc branch` and `arc bookmark` will still technically work, but the proper names of these workflows are now `branches` and `bookmarks`. You can also use `arc alias` to redefine these if you've developed muscle memory for the old commands. - The `arc.feature.start.default` configuration option has been removed. Specifying a startpoint is still supported (with `arc work --start Y`). You can use `arc alias` to define a convenient alias if you'd like a command which always starts from a particular branch. I don't currently plan to restore a configuration option for this, since this isn't a behavior that impacts other people working on a project and the default behavior (branching from the current state) is generally a desirable one.

**Changes and Compatibility Breaks** - `arc branch` is now `arc branches`. This read-only workflow shows branches in the working copy. It shows branches in every VCS (previously, it showed bookmarks in Mercurial). - `arc bookmark` is now `arc bookmarks`. This read-only workflow shows bookmarks in the working copy. It shows bookmarks in every VCS (previously, it showed branches in Git). - `arc feature`, and the write/checkout modes of `arc branch` and `arc bookmark`, are now `arc work` ("begin or resume work"). These changes are aimed at simplifying these commands, particularly in Mercurial. See T2928. Previously, it was fairly unpredictable that that `arc branch` showed bookmarks, and that `arc branch X` allowed you to //create// a bookmark, and that there were several different ways to accomplish the same goals, and that `arc bookmark X` //created a **branch**// in Git, which doesn't even have a concept of bookmarks. After these changes, exactly one command is used to accomplish each task regardless of the VCS. | Task | VCS | Old Command | New Command | |---|---|---|---| | Show branches. | git | `arc branch` or `arc bookmark` | `arc branches` | | | hg | Not Supported | `arc branches` | | Show bookmarks. | git | N/A | N/A | | | hg | `arc bookmark` or `arc branch` | `arc bookmarks` | | Work on a change. | git | `arc feature X` or `arc branch X` or `arc bookmark X` | `arc work X` | | | hg | `arc feature X` or `arc branch X` or `arc bookmark X` | `arc work X` Because `arc` automatically corrects the spelling of commands and accepts unique prefixes of commands as short variations, `arc branch` and `arc bookmark` will still technically work, `arc branch` and `arc bookmark` will still technically workbut the proper names of these workflows are now `branches` and `bookmarks`. You can also use `arc alias` to redefine these if you've developed muscle memory for the old commands. - The `arc.feature.start.default` configuration option has been removed. Specifying a startpoint is still supported (with `arc work --start Y`). You can use `arc alias` to define a convenient alias if you'd like a command which always starts from a particular branch. I don't currently plan to restore a configuration option for this, since this isn't a behavior that impacts other people working on a project and the default behavior (branching from the current state) is generally a desirable one.