Pushes performed by [email protected] despite scoped token about create-pull-request HOT 3 CLOSED

I think this behaviour is due to the recent v2 release of actions/checkout. I notice you are following the master branch of checkout with actions/checkout@master, so you are now using v2.

I haven't completely figured out how these changes affect this action yet. Not sure if this will solve your issue, but what you could try is setting the PAT on the checkout, too.

    - uses: actions/checkout@v2
      with:
        token: ${{ secrets.PAT }}
        ref: master

from create-pull-request.

That has solved the issue, thank you very much!

from create-pull-request.

@pauleve Just to let you know that recent versions of the action have fixed this problem and it shouldn't be necessary to checkout using the PAT. The action will now correctly use the PAT passed to it to push.

    - uses: actions/checkout@v2

    # Make changes to pull request here

    - name: Create Pull Request
      uses: peter-evans/create-pull-request@v2
      with:
        token: ${{ secrets.PAT }}

from create-pull-request.