Push to protected branch

[jchannon]

I have managed to get pushing to a branch working fine but I'd like to push to master which is a protected branch. However if I am on my local machine I can push to master, I assume as I am the owner of the org and repo? Is there any way to use the token or identify myself so the action can make a commit using my name and email and push to the protected branch?

[JamesHenry]

I have the exact same issue on typescript-eslint, you can see the configuration here:

typescript-eslint/typescript-eslint@19516de

And the resulting failure from running the action here:

https://github.com/typescript-eslint/typescript-eslint/runs/1084722742?check_suite_focus=true

---

This issue does seem to be specific to github actions. I have an Azure DevOps release pipeline using the exact same lerna configuration using the exact same PAT.

What is github actions doing differently?

Also FYI, A number of folks seem to be running into this and have reported it on the lerna repo here: lerna/lerna#1957

[slugbyte]

i was having the same issue and then i made a personal access token to use instead of the GITHUB_TOKEN

example

name: PUBLISH NPM PACKAGE
on:
  push:
    branches: [ release ]
jobs:
  run-checks:
    runs-on: ubuntu-latest
    strategy:
      matrix:
        node-version: [15.x]
    env: 
      KIIPO_BOT_NPM_AUTOMATION_TOKEN: ${{ secrets.KIIPO_BOT_NPM_AUTOMATION_TOKEN }}
    steps:
    - uses: actions/checkout@v2
      with:
        token: ${{ secrets.KIIPO_BOT_GITHUB_REPOSITORY_ADMIN_TOKEN }}
    - name: Use node version ${{ matrix.node-version }}
      uses: actions/setup-node@v1
      with:
        node-version: ${{ matrix.node-version }}
    - run: git config user.name "kiipobot"
    - run: git config user.email "superuser@kiipo.com"
    - run: npm ci 
    - run: npm run lint
    - run: npm run release:ci 

this allows me to push without problem, however it triggers a new push event which retriggers my action workflow. In effect a loop that contiues to update my package version number and publish it to npm.

so even though i can now push with a personal access token, its not a solution.

when i then disable my branch protections and use the original GITHUB_TOKEN i can push and it does not re trigger the push event

does anyone know how to use a personal access token to commit and push without re-triggering the push event ?

[AJ-7885]

If you are only update the version in package.json you can ignore it by file or path or even user, this would work file for your solution

[simondelphia]

Is there any way to configure it so the bot user can push to the protected branch without also being an admin?

[wojpawlik]

Deploy key bypasses branch protections, at least without "Require a pull request before merging". It's possible to skip ci if needed.