Branch History

Every branch in a versioned application keeps a record of its commits. Branch history lets Creators review what changed and when, and revert the branch to an earlier state if needed.

Open Branch History

To open the branch history for a branch:

1. In the module toolbar, click the checkout pill.

   

2. Select   Manage Versions.

3. On the branch to review, select   (ellipsis) >   Branch History.

The Branch History dialog opens. It lists commits newest first. Each row shows the action the commit performed, its abbreviated commit ID, the Creator who made it, and the timestamp. The dialog shows 10 commits per page — use the pager at the bottom to move between pages, or change the rows-per-page setting beside it.

The row shows the last seven characters of the commit ID. To copy the full ID, select (ellipsis) > Copy ID on that row.

View a Commit Read-Only

Viewing a commit opens the application as it stood at that point in time, without changing the branch. It is the way to check what a commit contains before deciding whether to revert to it.

To view a commit:

1. Open the Branch History dialog for the branch.

2. Locate the commit to view.

3. On that commit row, select   (ellipsis) >   View.

The dialog closes and the application reloads at that commit. While a commit is open:

• The checkout pill reads Historic commit followed by the abbreviated commit ID, with a   (history) icon.

• A banner below the tab bar reads: You are viewing a historic version of this branch. To use this version, revert to it first.

• The File Explorer lists the modules as they existed at that commit, and opening one loads it read-only. Save is replaced by a read-only notice.

A commit is never remembered as your branch. To leave the read-only view, use the checkout pill to switch back to a branch or version.

View does not display on the commit you are already viewing, that row is marked Current instead.

Revert to a Commit

Reverting to a commit sets the branch back to the state it was in at that point in time.

Reverting does not delete any history. The platform adds a new revert commit to the branch, so the full history is preserved. To undo a revert, revert again to the commit that came before it.

To revert to a commit:

1. Open the Branch History dialog for the branch.

2. Locate the commit to revert to.

3. On that commit row, click   Revert to.

4. Review the confirmation dialog and click Revert.

A confirmation message displays and the commit list refreshes to show the new revert commit at the top.

Reverting while viewing a commit read-only does not leave that view. Once the revert completes, use the checkout pill to switch back to the branch.

Reverting requires update permission on the application. The Revert to button does not display without this permission.