Skip to main content

​
vers history

Shows the commit history for the current VM or a specified VM ID or alias.

​
Usage

vers history                    # Show history for current HEAD VM
vers history [vm-id|alias]      # Show history for specific VM

​
Examples

​
Show current VM history

vers history
Displays commit history for your current HEAD VM.

​
Show specific VM history

vers history vm-abc123
vers history my-alias
Shows commit history for the specified VM.

​
Output format

Commit History for VM: my-web-server

Commit: c123456789abcdef
v1.0.0
Author: [email protected]
Date: Mon Jan 15 14:30:25 2024 -0700
VM: vm-abc123
Cluster: prod-cluster
Architecture: x86_64

    Add authentication feature

────────────────────────────────────────────────

Commit: c234567890abcdef
Author: [email protected]
Date: Sun Jan 14 09:15:10 2024 -0700
VM: vm-abc123

    Initial setup
Each commit entry shows:
  • Commit ID: Unique identifier for the commit
  • Tags: Version tags or labels (if any)
  • Alias: VM alias (if different from VM ID)
  • Author: Who created the commit
  • Date: When the commit was made
  • VM: VM identifier
  • Cluster: Cluster ID (if available)
  • Architecture: Host architecture (if available)
  • Message: Commit description

​
How it works

The history command:
  1. VM resolution: Uses HEAD VM if no identifier provided, otherwise resolves the specified VM/alias
  2. API query: Fetches commit history from the server for the target VM
  3. Display: Shows commits in reverse chronological order (newest first)
  4. Formatting: Applies consistent styling and separators between commits

​
Empty history

If no commits exist for a VM: 
Commit History for VM: fresh-vm

No commits found for this VM.
Run 'vers commit' to create your first commit.

​
Prerequisites

  • Valid VM identifier (or current HEAD VM)
  • Network connectivity to fetch commit data
  • VM must exist in your account

​
See Also