ci : create git tags for released docker images

[rgerganov]

When releasing a docker image for build number X, we should also create the corresponding git tag. This allows users to easily checkout the corresponding source tree for given docker image.

[Copilot]

Pull Request Overview

This PR adds automatic git tag creation for released Docker images. The purpose is to allow users to easily checkout the corresponding source code for any given Docker image by providing a git tag that matches the Docker image tag.

Key changes:

• Refactors tag determination logic to use a reusable action for generating source tag names
• Adds a step to create and push git tags when Docker images are published

[CISC]

LGTM, not sure if you can push a tag without setting permissions though, have you tested it?

[rgerganov]

LGTM, not sure if you can push a tag without setting permissions though, have you tested it?

I don't know how to test such changes. Any help is appreciated.

[CISC]

LGTM, not sure if you can push a tag without setting permissions though, have you tested it?

I don't know how to test such changes. Any help is appreciated.

Apply the changes to master in your fork and trigger the workflow.

[CISC]

BTW, just checking, is your intention to just make sure that bXXXX is tagged (in case release failed), or did you mean to create some other tag?

[rgerganov]

I want to make sure that we have bXXXX tags for every released docker image. For example there is server-cuda-b6571 image but there is no b6571 tag.

The end goal is to have straightforward way to get the source tree for every docker image.

[CISC]

LGTM, not sure if you can push a tag without setting permissions though, have you tested it?

I don't know how to test such changes. Any help is appreciated.

Apply the changes to master in your fork and trigger the workflow.

You probably want to cancel your Release workflow before it creates the tag, and then maybe for good measure test after a release has been made and tagged.

[CISC]

Yep, not allowed:
https://github.com/rgerganov/llama.cpp/actions/runs/18009905451/job/51239436263#step:4:8

[CISC]

Yep, not allowed: https://github.com/rgerganov/llama.cpp/actions/runs/18009905451/job/51239436263#step:4:8

You probably need to add contents: write to permissions.

[CISC]

Yay, success:
https://github.com/rgerganov/llama.cpp/actions/runs/18031102219/job/51307482145#step:4:9

[rgerganov]

Yes, it does work with the suggested changes, thanks for the help. I have also started the Release workflow to make sure it succeeds when tag already exists.

[rgerganov]

Both Release and Publish Docker image workflows run fine on my fork and create the correct tag. @CISC should we merge this?

[CISC]

Both Release and Publish Docker image workflows run fine on my fork and create the correct tag. @CISC should we merge this?

Yes, looks good, merge at will.