Tag support?

[axi92]

I came across the usecase that I need a tag created on the commit as well, does it makes sense to implement this feature as well or is it better to use a different tooling?

I am using an Github App token so I am able to use it in the rule bypass list.

My approach would be this for now:

      - name: Create Tag
        run: |
          curl -X POST \
            -H "Authorization: Bearer ${{ steps.app-token.outputs.token }}" \
            -H "Accept: application/vnd.github+json" \
            https://api.github.com/repos/${{ github.repository }}/git/refs \
            -d @- <<EOF
          {
            "ref": "refs/tags/${{ github.event.inputs.tag_name }}",
            "sha": "${{ steps.app-token.outputs.token }}"
          }
          EOF

Main reason for this is no extra dependencies.

PS: I will post my finished workflow later if somebody else needs it.

Edit: https://github.com/axi92/steam-workshop-scraper/blob/e47a06f6ab0f7f2d310bb256550bd07033d8a506/.github/workflows/release.yml

I realized that the tool i am using (release-it) creates a github release and that only works with a git tag so the tag for me already exists =)

You can close the issue if you like :)

[IAreKyleW00t]

This is a pretty interesting use-case, and I think it might be fairly easy to add in. The Action supports the ref input but assumes it will always be a branch Ref. All the API calls the Action makes should support any Ref, so let me see if I add it in!

[IAreKyleW00t]

@axi92 Just to clarify, are you looking to only update the Tag or update both the Branch and Tag? The Action is currently built and intended to only update 1 Ref, but adding support for additional Refs to update (to the same commit) could be something I can have it do.

[axi92]

My usecase is just that I make a new commit and then add a tag to that just created commit.
So you already have the ref because you just created the commit =)

My app on the release flow generates the changelog and uses your workflow to commit. Then I want to tag that just created commit with a version tag so I know whats the release version.

I hope I could explain what my plan was =)

[IAreKyleW00t]

Sorry for the delay! I think this should be good to go as of v1.5.0 - You can now target a Tag ref (eg: refs/tags/vX.Y.Z) with the Action and that Tag will be updated to point to the new commit. Any protections rules would still apply, which you already accounted for with your app credentials.

Can you give this a try and see if it does what you're expecting? Like before, the target Ref must exist ahead of time and only that single Ref will be updated (Tag in this case). Let me know how it goes, and feel free to close this out if everything looks good :)

      - name: Commit changes
        uses: iarekylew00t/verified-bot-commit@v1.5.0
        id: commit
        with:
          ref: refs/tags/${{ steps.version.outputs.new }}
          message-file: commitMessageFile
          token: ${{ steps.app-token.outputs.token }}
          if-no-commit: notice
          update-local: false # we don't need to pull the remote made changes via git to local
          files: |
            CHANGELOG.md
            package.json
            package-lock.json

[IAreKyleW00t]

@axi92 - Let me know if you've had a chance to test this. I think you will encounter a limitation with using your own Token that will cause the final commit to not be signed/verified. This is sorta by design with how the GITHUB_TOKEN works; usually people would use git directly to perform any changes and include their own signatures.

[axi92]

Thanks for implementing that feature, unfortunately I don't have the time and the requirement to work on a similar case that needs your workflow. You can close that ticket if you like.
But I have your repo ⭐-ed and will use it when I have a use-case next time =)

[IAreKyleW00t]

That’s fine! Feel free to reopen this if you run into issues later :)

[sp-aaflalo]

Hello @IAreKyleW00t,

Not wanting to highjack the issue, but I tested exactly this, and I can't get it to work:
https://github.com/scalepad/terraform-provider-litellm/actions/runs/16882761661/job/47822583432

[IAreKyleW00t]

@sp-aaflalo Interesting, let me look into this and see if there was something I overlooked. It looks like this is triggering on new version Tags that get pushed, so I’m wondering if there’s a weird API delay? It might be worth having the action just check the local git DB for the commit details, since it should be there anyways.

[sp-aaflalo]

I think I found the bug or anyway my "misuage":
https://github.com/IAreKyleW00t/verified-bot-commit/pull/164/files#diff-2ea4750851b34def3ddd617afa64e175a87064a29dbb9e6fd20eee6f1dd6dc93R24-R29

In the code, you check for startWith('tags') before you clean up the refs/ ^^'
It should remove refs/ first I think. In my case I sent refs/tags/v0.4.1

Nope that doesn't change anything if I remove the prefix.
Could be a delay, I can retry the action.
Edit:
Retry didn't fix it.