fix(ci): give deploy job write permissions#253
Merged
tschneidereit merged 1 commit intobytecodealliance:mainfrom Jul 22, 2025
Merged
fix(ci): give deploy job write permissions#253tschneidereit merged 1 commit intobytecodealliance:mainfrom
tschneidereit merged 1 commit intobytecodealliance:mainfrom
Conversation
tschneidereit
approved these changes
Jul 22, 2025
Member
tschneidereit
left a comment
tschneidereit
left a comment
There was a problem hiding this comment.
You're correct: the repo is configured to only give actions read access by default. If I understand the documentation correctly, this change should indeed fix things, so let's hope it does!
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
I'm not sure why I don't need this to deploy gh-pages on my fork, but hopefully this will fix the CI:
https://github.com/bytecodealliance/StarlingMonkey/actions/runs/16442845527/job/46467489433
Another possible issue might be that the workflow permissions for repo (settings > actions > general) are set to read only. I don't have access to verify this.