Grant write permission to the publish-website action

[swankjesse]

No description provided.

[swankjesse]

In an attempt to fix this failure.
https://github.com/lysine-dev/okio/actions/runs/29934672801/job/88978978141

[command]/usr/bin/git add --all .
[command]/usr/bin/git checkout -b github-pages-deploy-action/phmv36a9p
Switched to a new branch 'github-pages-deploy-action/phmv36a9p'
[command]/usr/bin/git commit -m Deploying to gh-pages from  @ 0ed6b03a1a001a1bfcdc18f6658c41500be21d1a 🚀 --quiet --no-verify
[command]/usr/bin/git push --force ***github.com/lysine-dev/okio.git github-pages-deploy-action/phmv36a9p:gh-pages
remote: Permission to lysine-dev/okio.git denied to github-actions[bot].
fatal: unable to access 'https://github.com/lysine-dev/okio.git/': The requested URL returned error: 403
Running post deployment cleanup jobs… 🗑️
[command]/usr/bin/git worktree remove github-pages-deploy-action-temp-deployment-folder --force

[JakeWharton]

I think this should just be on the deploy step. Otherwise it's a potential supply chain attack across all actions instead of just that single one.

[swankjesse]

I think it’s gotta be on the entire job unfortunately. This is on master so if we get hacked there, we’re already hacked there.