Skip to content
ELYRA

Commit history

Browse the repository commits and see exactly what each one changed, without leaving the screen.

View Markdown

The Commits section lists the history of the project repository. It is read on demand: the panel only loads the history when you open the section.

Reading the list

Each row brings the data that identifies the commit:

  • the message and the author;
  • the date, in relative form (“2 h ago”) and exact when you need it;
  • the position relative to the comparison base — the panel distinguishes what is on this branch from what is already on the base.

The section header says what the list is being compared against, and offers See more commits to load the continuation of the history. This means the list is paginated: it does not show the whole repository at once.

Seeing what a commit changed

Opening a commit shows the details: metadata, the list of files it touched and the content of each change.

  • Each file opens the commit’s diff, with the before and after.
  • Binary file has no text preview: the panel says so instead of showing garbage.
  • If a file’s diff cannot be read, the panel says it failed and offers Try again — instead of leaving a blank space looking like the file didn’t change.

Opening a commit is pure reading: nothing changes branch, nothing is applied to your checkout.

Limits and scope

  • The reading is paginated. Don’t treat the list as the repository’s complete history.
  • Merges and binaries have their own handling. The diff of a merge commit and that of a binary file do not read like the diff of a text file.
  • History is reading, not undo. There is, in this section, no action to revert, apply or delete a commit. Undoing history is a terminal operation, with the care it demands.
  • A repository without commits has nothing to list; the panel says so instead of showing an error.

See also