Specify required permissions in README #164
Merged
Conversation
This file contains 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
|
This helped me a lot, I'd like to see it in the documentation. |
softprops
reviewed
Sep 27, 2021
|
|
||
| ```yaml | ||
| permissions: | ||
| contents: write |
There was a problem hiding this comment.
I'll take your word for it but I haven't verified this myself
There was a problem hiding this comment.
I just tested it and can confirm that it fixed the "Resource not accessible by integration" for me. 👍
|
thanks fo rthe pull @danepowell |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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 attempted to implement this action and was stymied by the following error:
Our org had Actions repo access set to read-only. Even knowing that, it wasn't clear what permissions were required to actually fix the actions. Experiments reveal probably just
contents: write. I'm a little surprised, I would have expectedpackages: writeas well?Downstream issue where we encountered this problem: acquia/cli#654
Previous issue, where this should have been documented more visibly: #96