github-push-action | updated code | Continous Integration library

I don't how to fix that to push the commit to the branch itself connected to the tag as i need to update the kustomize.yaml there after each building

As far as Git itself is concerned, there is no connection between a branch name and a tag name.

At the Git level, any name—any reference—is simply a name that stores a hash ID. Branch names in particular are constrained to store only commit hash IDs, while tag names can store the hash ID of any internal Git object. A tag is said to be a lightweight tag if it stores a commit hash ID, or an annotated tag if it stores the hash ID of a tag object. This tag object then typically stores the hash ID of some commit.

You can use git branch --points-at to find branch names that select some particular commit, and git tag --points-at to find tag names that select some particular commit. For details, see the git branch and git tag documentation.

Note that you can give git tag the commit hash ID here, and it still finds annotated tags. Technically, it finds the annotated tag regardless of whether you name the tag object itself, or its target commit:

Under the devmasx/merge-branch@v1.3.1 action, you need to replace

the line github_token: ${{ github.token }}

with github_token: ${{ secrets.GITHUB_TOKEN }}

Next, since you are getting error in commiting files I would recommend you to use

After a bit of digging I found out the solution. branch name is found in github.event.release.target_commitish env variable.

Scheduled GitHub Actions run on the default or base branch, as specified by the documentation:

Scheduled workflows run on the latest commit on the default or base branch.

Which means that your workflow file must be committed to the master branch. It then can check out code from other branches, but the workflow file itself must reside in master.

Here is the most minimal example that demonstrates how it works.