Using Version History

Following are a few things to know about the version history:

• The last committed version always displays in the repository area. When the history is expanded it shows from the end, not the beginning. In other words, the latest version displays first at the top of the list, and older versions move down in the list.

• The edits number can get high (e.g., 254 edits). Edits are counted per action (i.e., roughly one character change equals one edit). The system controls the count of edits by auto-bundling changes (i.e., creating a working version of the file in the repository) between commits, every 30 minutes.

• The version history is updated based on the branch; and there is only one workspace per branch.

• Using Version History
  • How to View a Previous Version
  • How to Revert to a Previous Version

[Menu Proxy — Headings — Online — Depth3 ]

1. On the left side of the Flare Online interface, click Projects.

2. Select a project to open it.

3. Click the Workspace tab at the top of the screen.

4. (Optional) From the drop-down at the top of the interface, you can select a branch for the edits.

5. From the left side of the page, select a file. The last committed version displays in the editor, and the version history area shows on the right side of the screen.

6. In the version history area, click Show History. Upon selection the button changes to Hide History—so you can collapse the history. If revisions exist for the file, the timeline expands to show the versions (i.e., original when it was created, auto-bundled saves between commits, and committed files.)

   

7. Select a previous version. (To select an auto-bundled version, you might need to click the down arrow to expand the timeline further.)

8. The editor displays the version selected. You might notice older edits.

9. Click Go to Workspace to return to the current working version.

   

You can revert to a previous version of the file (i.e., to the original version, a committed version, or an auto-bundled version).

1. On the left side of the Flare Online interface, click Projects.

2. Select a project to open it.

3. Click the Workspace tab at the top of the screen.

4. (Optional) From the drop-down at the top of the interface, you can select a branch for the edits.

5. From the left side of the page, select a file. The last committed version displays in the editor, and the version history shows on the right side of the screen.

6. In the version history area, find the instance of the file that you want to restore. (You might need to click Show History or expand auto-bundled versions in the timeline.)

   Tip It might be a good idea to select the version and view it first, before reverting it, just to make sure that version is the one you want.

7. Click (Revert to this version).

   This action copies the version as a new version, and records it as such in the workspace section.

   

8. The Revert dialog opens. If no other users are editing the file and it is safe to revert it, click Revert.

   

   Note If other users are detected as working in the file that you want to revert, the Revert dialog will warn you.

   

   In this case, you might want to click Cancel. Then, communicate with other team members about the conflict, and decide what action to take that works for your team.

9. Even though the revert updates the workspace version to what it was, it still needs to be committed to the repository. Click Commit in the upper-right corner of the editor.

10. In the Create New Commit dialog, enter a Commit Message.

11. Click Commit. The reverted file displays as the latest committed version in the repository.