Default Branch should be triggered branch not Master

The reason for this is because i was having hair pulling troubles trying to figure out how to get this action to push to the branch that triggered the script. Due to the complexity of github actions.

In addition, this Action name’s “intent” is just push, which by default I would expect it to only push on the triggered branch, not merge to master.

Either it should by default push to trigger branch or give the example to do so in the readme file.

      uses: ad-m/github-push-action@master
      with:
        github_token: ${{ secrets.GITHUB_TOKEN }}
        branch: ${{ github.head_ref }}

[Gummibeer]

@koppor

The former is for the .yml file (Syntax: GitHub Actions), the latter is inside https://github.com/ad-m/github-push-action/blob/master/start.sh (Syntax: Bash).

The advantage of the latter approach is that the script will also work when triggered in a push. Otherwise, it will only work in a pull_request event. (As far as I did not do something wrong in my experiements this morning. There, the variable github.head_ref was empty in the case of a push event)

You can use the ref instead of head_ref for push events. https://help.github.com/en/actions/automating-your-workflow-with-github-actions/contexts-and-expression-syntax-for-github-actions#github-context

[jcislinsky]

I set our CI to use this plugin to push only tags. So I didn’t set branch and I thought that it will push only tags. But a very weird thing happened. Every time our workflow finished a deploy from any branch it ‘force’ pushes the current branch to the master. 😲

Maybe I did not read the documentation properly but I still think that if I don’t specify the branch, it should push to the current or doesn’t push branch at all.