Permission denied to github-actions[bot]

Question

I'm using mkdocs to generate documents for my project,now I can't deploy those docs to Github pages,it tell me:

remote: Permission to XXX.git denied to github-actions[bot]. fatal: unable to access 'XXX': The requested URL returned error: 403

And my secrets of the repository:(The two GIT_ACTIONS_PUSH are all my personal access tokens.)

And if I start the CI process manually, CI will crash like this.

How can I solve it?

score 53 · Answer 1 · edited Feb 02 '23 at 23:35

53

Check if "Read and write permissions" are enabled in Settings -> Actions -> General -> Workflow permissions:

Workflow permissions Setting

edited Feb 02 '23 at 23:35

tdy

answered Feb 01 '23 at 09:44

yu xiangxiang

If he's using his own personal token, why does this setting which claims to affect the permissions of GITHUB_TOKEN have any effect on his attempt to push? – Abraham Murciano Benzadon Apr 14 '23 at 20:17
1

Workflows are disabled on repo forks by default, you have to manually enable them. Good catch! – InsertCheesyLine May 30 '23 at 09:15
Github does not allow me to give read and write permission – fccoelho Jul 21 '23 at 12:10

score 6 · Answer 2 · answered Jul 09 '23 at 00:57

6

If you're creating new files then you need to give explicit write permissions

permissions:
  contents: write

answered Jul 09 '23 at 00:57

Ewan

This is a better solution than the highest voted one because it limits the permissions to the minimum. – psmith Aug 12 '23 at 06:59

Arkadip Bhattacharya · Answer 3 · 2022-07-04T04:19:08.443

0

I think the persist-credentials: false and fetch-depth is the issue. It is deleting the credentials of the git while checking out the repository.

You can try removing the line and try.

    - uses: actions/checkout@v3

edited Jul 04 '22 at 04:19

answered Jul 04 '22 at 04:09

No，it has no help，and the crash is same. – forestbat Jul 04 '22 at 04:15
I don't think it has connection with fetch-depth. – forestbat Jul 04 '22 at 04:36

score -2 · Answer 4 · answered Jan 09 '23 at 18:39

-2

You need to update the Actions permissions on the repo as shared here

answered Jan 09 '23 at 18:39

Mike Mwanje

4 Answers4