github-token clarification…

[ghost]

I have a protected main branch with admins allowed to push and a private token from an admin account set as github-token: ${{ secrets.ADMIN_RELEASE_TOKEN }}. However, when running the action, I get:

remote: error: GH006: Protected branch update failed for refs/heads/main.       
remote: error: At least 1 approving review is required by reviewers with write access.

The token I use has delete:packages, repo, write:packages permissions. Should it have more or did I find a bug?

[TriPSs]

Hi @ygworldr, sadly I'm not quite sure yet on how to fix this. There is this medium article that describes it on how to achieve this.

[ghost]

I do not use an automatic build on commit to main, instead, I use the manual way to kick an action. This means I can remove protection, launch the action, and re-create protection as soon as the release is done. A little clunky but not too bad.

[xsc27]

Would deploy keys, issue #115, resolve this? I think it could be a cleaner workaround.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[xsc27]

TIL: Deploy keys and GitHub Apps will not get around protected branches that require a pull request, i.e.:

[vtertre]

Hi @ygworldr, sadly I'm not quite sure yet on how to fix this. There is this medium article that describes it on how to achieve this.

If it can save anyone some time, at this date you still have to use your PAT on the checkout step also, and not only on the TriPSs/conventional-changelog-action to push to protected branches.