Skip to main content

​
Undoing a commit

Committed something and wish you hadn’t? You can undo it. Diversion creates changes that are the opposite of that commit, and you commit them like any other change. From the CLI, use dv revert.
1

Go to your repo history

Open the workspace of the repo where your changes are. Make sure that you have no pending changes. In the left navigation rail, click Commits.
2

Select the commit to undo

Hover over the commit, click the … icon at the right of its row, and select Undo this commit…. In the dialog, click Undo changes. You may need to resolve a merge conflict first, as described in the last step.
3

Admire your work

Your workspace now has pending changes that reverse the commit. For example, if the commit changed a line in a file, the file shows as modified with that line changed back. Commit these changes to finish the undo.
4

Resolve a merge conflict?

If a later commit also changed a file that the undone commit touched, you get a merge conflict. For example, undoing the commit that created a file would delete it, but if a later commit modified that file, the two changes conflict. Resolve the conflict, as described in Conflicts, before you commit.

​
Editing a commit message

Made a typo in your commit message, or want to add more detail? You can edit the message of any commit you authored directly from the Commits view.
Editing commit messages is only available for the commit author, and is not supported for repositories synced with Git.
1

Open the commit menu

In the Commits view, hover over the commit whose message you want to change, click the … icon at the right of its row, and select “Edit commit message”.
2

Update the message

An “Edit commit message” dialog will appear, showing the commit ID for reference and a text area with the current message. Edit the message as you like, then click “Update” to save it.

​
Cherry-picking a commit

Cherry-picking lets you take a specific commit from the history and re-apply its changes into your current workspace. This is useful when you want to bring in a particular change without merging an entire branch. Your workspace must have no uncommitted changes before cherry-picking. Cherry-picking is not available for the initial commit of a repository. In the Desktop App:
1

Find the commit in Commits

Open the Commits view and find the commit you want to cherry-pick.
2

Open the cherry-pick dialog

Right-click the commit, or hover over it and click the … icon at the right of its row, and select Cherry-pick into workspace….
3

Choose what to apply

The dialog lists the files the commit changed, all selected. To pick only part of the commit, uncheck the files or folders you don’t want, then click “Cherry-pick”. The selected changes are applied to your workspace without being committed.
4

Resolve conflicts if needed

If the cherry-picked changes conflict with your current workspace, you’ll be taken to the merge conflict resolution view. See merge conflicts for details on resolving them.
A renamed file is picked by its new path. Picking the new path also removes the old one. The same options are available from the CLI, where you name the files and folders to pick after the commit ID. See the cherry-pick command for details.

​
Copying commit details

Need to reference a specific commit in a conversation or a script? You can quickly copy a commit’s ID or message straight from the Commits view.
1

Copy commit ID

In the Commits view, hover over a commit, click the … icon at the right of its row, and select “Copy commit ID”. The ID is copied to your clipboard right away — you’ll see a “Copied commit ID” notification confirming it.
2

Copy commit message

Similarly, you can select “Copy commit message” from the same menu to copy the full commit message text to your clipboard.