Revision History

Every time a paste is edited, SnipShare saves a revision for each file that changed. Revisions let you see the full history of a paste and compare any two versions side-by-side.

---

How Revisions Work

When you save an edit:

• Only files that changed get a new revision record - unchanged files are not duplicated
• The paste’s version counter increments
• The new revision stores the full file content, filename, language, version number, change author, and an optional change note
• The paste retains its original share_hash - the URL never changes

---

Viewing Revision History

Navigate to the revision list at:

/paste/{hash}/revisions/

This page shows a list of all revisions for the paste. Each entry displays:

• Version number
• Which file was revised
• Author and timestamp
• Change note (if provided)

---

Comparing Two Versions

View a diff between any two versions:

/paste/{hash}/diff/{v1}...{v2}

Example: /paste/abc123/diff/1...3 compares version 1 with version 3.

The diff view shows:

• Added lines in green
• Removed lines in red
• Unchanged context lines

---

Writing a Change Note

When editing a paste, you can optionally fill in a Change Note field (maximum 500 characters). This note is stored with the revision and appears in the revision history list.

Good change notes make it easy for you and collaborators to understand what changed and why:

Fixed null pointer in the helper function when $user is empty

---

Access Control

• Owner can always view revisions and diffs for their own paste
• Visitors can view revisions and diffs for public and unlisted pastes
• Private paste revisions are only visible to the owner
• Password-protected pastes require unlock before viewing revision history

---

Notes

• Revisions are per-file - the same version number may correspond to different files within the same edit
• Revisions are stored indefinitely and are not pruned automatically
• Forking a paste does not carry over the revision history - the fork starts at version 1