Skip to content

Commits

Commits tells you what has been done in your GitHub repositories: the commits of a period, who made them and when. It works with several repositories at once and, when the work lives on feature branches, it can read every branch without counting the same commit twice. It also reads one commit with the files it changed and compares two branches or versions.

When to use it

  • A weekly project report: how many commits, by whom and in which repository.
  • A voice or chat agent that answers “what was done this week?” or “how many changes has Hermes pushed since Monday?”.
  • Knowing what is still to be deployed: what the dev branch has and main does not.
  • Checking which files a given commit touched.

Configuration

You need a GitHub API credential. A fine-grained token with read access to Contents and Metadata on the repositories is enough. See Credentials.

FieldWhat it does
Credential (required)The GitHub API credential.
Operation (required)List Commits, Get Commit or Compare.
Repositories (required)owner/repo, or just the name when the credential sees a single repository by that name. For List Commits and Compare, several separated by commas, or a pattern with *: my-org/web-* reads every repository of my-org whose name starts with web-.
BranchList Commits: the branch, tag or SHA. Empty: the default branch. *: every branch; each commit appears once, with the branches it is on.
Since / UntilFrom and to when: a date (2026-11-02), today, yesterday or a span back from now such as 7d, 24h or 2w. Defaults to the last 7 days.
AuthorOnly commits by this GitHub user or email.
PathOnly commits that touch this file or folder.
ResultCommits: one item per commit. Summary: a single item with totals by repository, author, branch and day, and the latest commits of each repository.
CommitGet Commit: the SHA, full or its first 7 characters.
Base / HeadCompare: what Head has that Base lacks (branches, tags or SHAs).
Include changed filesAdds the files and lines changed to each commit. One extra request per commit: slower on long lists.
LimitMost commits read per repository (300 by default).

Output

  • List Commits with Commits: per commit, the repository, SHA, title and message, author (name, email and GitHub user), date, whether it is a merge, link and branches. Newest first.
  • List Commits with Summary: total commits and merges, breakdown by repository, author, branch and day, and the latest of each repository.
  • Get Commit: the commit with its files, lines added and removed, and its parents.
  • Compare: for each repository, the status (ahead or behind), how many commits apart, the list of commits and the files changed. A repository without that branch, tag or SHA brings the error and the others are compared all the same.

When no commit matches the filters it returns a single item saying so, not an empty list.

As an agent’s tool

Connect Commits to the tools port of an Agent or a Voice Agent. Keep Repositories fixed on the node (e.g. my-org/project-*) and let the AI fill the dates, author, branch and format. With Summary, the agent answers “how many commits this week?” with a single call. See Tool Mode.

Example

A Friday report with the activity of a project’s three repositories:

  1. Add Commits with List Commits, Repositories my-org/westfield-*, Branch *, Since 7d and Result Summary.
  2. Connect its output to a model that writes the summary in three sentences.
  3. Send the result by email and schedule the flow on Fridays at 14:00.