Add commit hash/tag to workflow runs list

[kogratte]

Why are you starting this discussion?

Question

What GitHub Actions topic or product is this about?

Misc

Discussion Details

May it be possible to add the commit / tag that has been used to run a workflow? For the time being, you need to open the run logs to see from where it comes, which is heavy.

[vanhuy2005]

Hi @kogratte,

Yes, it is absolutely possible. You can display the commit hash or tag right in the workflow list without opening the logs. You can use the run-name property. This allows you to print the Context variables (like commit SHA or Tag name) directly in the title of the workflow run.

Add this to the top level of your workflow YAML file:

//Display Branch/Tag name and short Commit Hash
run-name: ${{ github.ref_name }} - ${{ github.sha }}

The result instead of a generic title, you will now see something like: main - 8a2b3c... or v1.0.0 - 9d8e7f... right in the Actions list.

Hopefully it can help you!

[kyyasilmyradovv]

Hey Friend 👋

Yes — you can show the commit or tag directly in the workflow run title so you don’t need to open logs anymore.

✅ Solution: Add commit / tag to the workflow run name
name: CI – ${{ github.ref }} – ${{ github.sha }}
This will display the tag or branch name and the commit SHA right on the workflow run list, making it easy to see where each run came from.

You can also show only what you need:
Show tag (if exists) or branch:
run-name: "Run from ref: ${{ github.ref_name }}"

Show short SHA:
run-name: "Commit: ${{ github.sha }}"

Now the workflow list will clearly show which commit/tag triggered each run — no need to open logs.

[kogratte]

Oh, clever solution! But It also means the run name may become heavy as the time fly, as many people are using it to display other information as well (like selected options for a run). It makes me think that maybe my request was not so clear. It may be worth adding a resume of workflow run inputs, eliminating the need of a deep dive. For example, we're currently using run name to display selected arch and os, that may be multiples. It forces us to do some ternary magic, but listing workflow inputs in a smart way may be much cleaner! Thoughts? Le mer. 26 nov. 2025 à 10:43, Kyyas Ilmyradov ***@***.***> a écrit :

…

Hey Friend 👋 Yes — you can show the commit or tag directly in the workflow run title so you don’t need to open logs anymore. ✅ Solution: Add commit / tag to the workflow run name name: CI – ${{ github.ref }} – ${{ github.sha }} This will display the tag or branch name and the commit SHA right on the workflow run list, making it easy to see where each run came from. You can also show only what you need: Show tag (if exists) or branch: run-name: "Run from ref: ${{ github.ref_name }}" Show short SHA: run-name: "Commit: ${{ github.sha }}" Now the workflow list will clearly show which commit/tag triggered each run — no need to open logs. — Reply to this email directly, view it on GitHub <#180444 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAORHVNBV4JLW3NV2ZYIAFT36VY2TAVCNFSM6AAAAACNHOJDQGVHI2DSMVQWIX3LMV43URDJONRXK43TNFXW4Q3PNVWWK3TUHMYTKMBYGQ2TCNQ> . You are receiving this because you were mentioned.Message ID: ***@***.***>