Branch Commits Tab

The Commits tab displays all commit records for a branch including baseline, feature commits, and merges, with filters to track activity by author or date.

Every change made in a branch is stored as a commit. This includes:

• Baseline Commit – created automatically when the branch is initialized from Main or another source.

• Feature Commits – individual commits made when developers edit, add, or delete components.

• Merge Commits – created when one branch is merged into another.

Commits provide a complete timeline of changes in the branch and serve as the audit trail of development.

Commit Details

Each commit record shows:

• Commit Name – usually tied to a story, merge, or developer action.

• Author – the user who performed the commit.

• Timestamp – when the commit was made.

• Commit Hash – a unique identifier that links to the exact snapshot of changes.

Clicking a commit opens its details where you can see the specific components modified in that commit. Each component shows exactly what was added, removed, or updated.

Filtering Commits

To help you locate changes quickly, you can filter commits using:

• Author – view commits made by a specific developer.

• Date Range – narrow down commits by calendar selection.

• Search Box – type keywords or commit names.

Commit Differences

When you open a specific commit, Revvy displays the diff view:

• Additions are highlighted in green.

• Deletions are highlighted in red.

• XML or code changes are shown line by line for precise tracking.

This makes it easy to review what changed in the commit before validating or deploying.

Best Practices

• Write meaningful commit messages that describe the change clearly.

• Use commits frequently to keep branch history detailed and traceable.

• Always review commit diffs before merging or deploying changes.