Skip to content

Conversation

samweaver
Copy link
Member

A few tweaks to the security concepts doc:

  • Tidied up the titles
  • Reordered some paragraphs
  • Added a new section at the end about application configuration

Summary

Labels

Test Plan

Checklist

  • If required, I have updated the Plural documentation accordingly.
  • I have added tests to cover my changes.
  • I have added a meaningful title and summary to convey the impact of this PR to a user.
  • I have added relevant labels to this PR to help with categorization for release notes.

A few tweaks to the security concepts doc:

- Tidied up the titles
- Reordered some paragraphs
- Added a new section at the end about application configuration
@samweaver samweaver requested a review from a team as a code owner April 28, 2023 11:28
@netlify
Copy link

netlify bot commented Apr 28, 2023

Deploy Preview for pluraldocs ready!

Name Link
🔨 Latest commit 8cd16ab
🔍 Latest deploy log https://app.netlify.com/sites/pluraldocs/deploys/645406f742f0820008c4a02b
😎 Deploy Preview https://deploy-preview-197--pluraldocs.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

## GitHub
## What permissions does Plural have to GitHub?

Plural **does not** have access to repositories that have not been created by Plural.

When using the CLI or Cloud Shell, Plural will receive the following permissions:

- Create GitHub repositories on your behalf
- Commit changes to repositories that Plural has created
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We should make it clear that we only get use the access token while creating the repo then throw them away as well

@michaeljguarino pls review additions and merge if you like.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants