https://infracost.io logo
Join Slack
Powered by
This message was deleted.
# general
b
This message was deleted.
c
Great question! I will look into this and document but off the top of my head I would guess you also need 
pull_request: write
or maybe 
issues: write
. I don’t think 
discussions: write
is needed.
p
is contents: write required, since a tmp file is writte?
Copy code
id-token: write
      contents: read
      pull-requests: write
trying this now
seems like 
pull-requests: write
did the trick. Thanks
👍 2
c
I don’t think 
contents: write
would be needed since we’re just writing to the file system and not using the api to modify anything. https://docs.github.com/en/rest/reference/permissions-required-for-github-apps#permission-on-contents
I guess if you were uploading artifacts in your action you may need that
w
I tweaked the docs to clarify this issue. Does that help?
p
Yeah thats good, but maybe also add the 
permissions:
setting to an examples workflow?
w
@plain-ocean-92335 good idea - I added this just now, all examples have this comment line that sends people to the action’s readme for other options
Copy code
behavior: update # Create a single comment and update it. See <https://github.com/infracost/actions/tree/master/comment> for other options
7 Views
Open in Slack
PreviousNext
Powered by