-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: Add documentation of restricting permissions #53
Conversation
The tests fail because the installation of the latest dmm release still needs access to raw.githubusercontent. Should i remove this bit from the ci? as it doesn't reflect PR's but just shows installing dmm works. Otherwise, it would show our ci fails, but the ci would pass after a new release |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM. sorry for late review
looks like this branch needs to be updated before being merged |
btw, im pushing the docs related to this issue to staging |
Np, i'll probs leave it (merging) until #62 is merged cause theres gonna be more conflicts |
Fixes #45
Description
Update docs to use more restrictions when using permissions
Use current logic and cdn.deno.land to get latest std release. The reason for this was we don't have to add 'raw.githubusercontent' into the
--allow-net
permission. Plus, the cdn provides the latest std version so the logic was pretty just pointless extra codeOther Notes