Does not trigger github workflow after auto update merge about autoupdate HOT 5 CLOSED

@mertnacakgedigi I believe this is expected, but I discovered that you could actually use a Personal Access Token (PAT) instead of GITHUB_TOKEN which should do the trick.

Would looks something like this:

name: autoupdate
on:
  pull_request:
    types: [auto_merge_enabled]
jobs:
  autoupdate:
    name: autoupdate
    runs-on: ubuntu-18.04
    steps:
      - uses: docker://chinthakagodawita/autoupdate-action:v1
        id: autoupdate
        env:
          GITHUB_TOKEN: '${{ secrets.MY_PAT }}'
          MERGE_CONFLICT_ACTION: 'fail'

      - run: echo 'Merge conflicts found!'
        if: ${{ steps.autoupdate.outputs.conflicted }}

      - run: echo 'No merge conflicts'
        if: ${{ !steps.autoupdate.outputs.conflicted }}

I think it's still a good idea to have this issue, but instead, the README should be updated to talk about this alternative authentication token.

from autoupdate.

Created a feature request discussion to hopefully get GitHub to make this a bit clearer: community/community#21091

from autoupdate.

Using Personal Access Token triggers the subsequence workflows. Thanks @Julian88Tex

from autoupdate.

Hm, actually maybe GITHUB_TOKEN permissions can be modified: https://docs.github.com/en/actions/security-guides/automatic-token-authentication#modifying-the-permissions-for-the-github_token

from autoupdate.

Thanks @Julian88Tex. We don't prefer using PAT for our organization. I'm still looking for a workaround for this.

from autoupdate.