docs: clarify policy names#164
Merged
dcmiddle merged 1 commit intoconfidential-containers:mainfrom Mar 4, 2026
Merged
Conversation
Address feedback for consistent use of policy names And clarify that filenames are arbitrary Signed-off-by: Dan Middleton <dmiddleton@nvidia.com>
✅ Deploy Preview for frolicking-manatee-96c0c8 ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
fitzthum
approved these changes
Mar 4, 2026
Member
fitzthum
left a comment
fitzthum
left a comment
There was a problem hiding this comment.
LGTM. Time to introduce another policy
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.
Address feedback for consistent use of policy names And clarify that filenames are arbitrary