Whenever a new version of a file is checked into the Helix Server, a commit record is created. Begin browsing the history of commits by clicking the Commits link in the main toolbar.
When you are viewing a particular file or directory, clicking the Commits tab displays the commits for that location in the depot.
The Range field lets you filter the list of changes for the depot path being viewed. When you click the Range field, a dropdown syntax guide appears providing sample commit filtering expressions.
The expressions that can be used within the Range field include:
A file's commit history presents each version of a file that the Helix Server knows about, including the change number, userid, change description, time ago, along with Open and Download buttons.
Swarm also displays contributing commits when available, such as when a file has been renamed, or integrated from another location in the Helix Server.
If a commit represents a deleted revision, the Open and Download links are replaced with a trashcan icon to indicate that this version is no longer available.
When your Helix Server has a remote depotA depot located on another Helix Server accessed by the current Helix Server. configured, you can browse the contents of the remote depot, but remote depots do not share their commit history. If you attempt to view the commits of a file provided by a remote depot, Swarm displays: