Short answer: You can list commits in GitHub by hand from its own interface, but it won’t repeat itself. On TinyCommand, add the GitHub List Commits action to a workflow, map its 6 inputs from any upstream app, and it runs automatically every time the trigger fires. No code, and a free tier to start.
Every field can be mapped from an upstream trigger, AI step, table row, or hard-coded literal.
| Field | Type | Required | Description |
|---|---|---|---|
Repository Owner owner | string | Required | GitHub repository owner — the user or organization login (the part before / in owner/repo URLs). |
Repository Name repo | string | Required | GitHub repository name — the part after / in owner/repo URLs. Not the full URL. |
Branch / SHA sha | string | Optional | Git commit SHA (full 40-char hex, or shortened 7+ chars). |
Author author | string | Optional | GitHub login or email to filter by |
Since since | string | Optional | Only commits after this ISO 8601 date |
Per Page per_page | string | Optional | Per Page. e.g. "30" |
{"owner": "e.g. acme-corp","repo": "e.g. my-project","sha": "e.g. main","author": "e.g. johndoe","since": "e.g. 2025-01-01T00:00:00Z"}
[{"sha": "abc123def456","commit": {"author": {"date": "2025-01-15T12:00:00Z","name": "John Doe"},"message": "Fix login redirect on Safari"},"html_url": "https://github.com/acme-corp/my-project/commit/abc123def456"}]
Use these fields in downstream nodes for routing, logging, or error handling.
Any of these apps can fire this action as part of a workflow.