- * When we detect the replay cause on the current run we lookup the original run and return its changesets.
- It turns out the first cause in the array is the least significant to display. For example, a replayed run has two causes:
- If there are two or more causes on the run then the last cause in the array is more important to the user than the changeset message when viewing Activity or Branches tabs.
- e.g. The fact that a run was replayed is more interesting than its changeset messages