Skip to main content

Reviewing Commit History

The Commits tab in the Version Control panel lists the commit history of the branch you currently have checked out. Use it to confirm what actually landed on a branch — after a pull request is merged, before you publish, or when you need to tell whether a colleague's change reached your local copy.

Before you begin​

  • The application must be Git-enabled and have at least one commit.
  • The history shown is for the branch you have checked out. To read another branch's history, check that branch out first.

Reading the history​

  1. Open your Git-enabled application and select the Version Control icon in the right sidebar.
  2. Select the Commits tab.
  3. The ten most recent commits load. Each entry shows:
    • The commit message
    • The abbreviated commit hash
    • The author's name
    • How long ago the commit was made, shown as 5m ago, 3h ago, or 2d ago for the past week, and as a date beyond that
  4. Select Load more commits at the bottom of the list to load ten more. When Koodisi can estimate how many commits remain, the button reports the count.

The most recent commit is highlighted, so you can see at a glance whether the tip of the branch is the change you expected.

Searching​

Enter text in the search field to filter the loaded commits by message or author name. The search applies to commits that are already loaded, so select Load more commits first if you are looking for something older.

Copying a commit hash​

Select the abbreviated hash on any commit to copy the full hash to your clipboard. Koodisi confirms with Commit hash <hash> copied to clipboard. Hover the hash to see the full value before copying.

A full commit hash is what you need when you are cross-referencing a Koodisi commit against a pull request in your Git provider, or matching a deployment back to the commit it was published from.

How you know it worked​

The commit you are looking for appears in the list with the expected author and message. After a merge in your Git provider, check out the target branch, select Pull, then open the Commits tab — the merged commit appears at the top.

When it does not work​

SymptomCauseWhat to do
Failed to fetch git log. Please try again.The commit history could not be read for the checked-out branch.Select the refresh icon next to the search field. If it persists, confirm the application is present locally and has an initial commit.
No commits foundThe branch has no commits, or the application has not had an initial commit yet.Stage and commit your changes on the Changes tab.
A colleague's merged commit is missingYour local copy has not been updated since the merge.Select Pull, then reopen the Commits tab.
Commits show an author you do not recognizeA pull that merged remote commits records the merge under Koodisi's internal author, or several developers shared one credential.Have each developer set their own Credentials at session start.
The history is not the branch you expectedThe Commits tab follows the checked-out branch.Check the branch name at the top of the Version Control panel, and check out the branch you meant.

Next steps​