docs: internal docs for trusted publishers #13537
Merged
Conversation
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
Signed-off-by: William Woodruff <[email protected]>
|
question: seeing as these are internal docs, should they be placed in a dev docs section instead? |
Possibly -- I wrote these more as "retrospective" details (for other package indices to benefit from) rather than concrete implementation details that would help a Warehouse contributor, but I have no strong opinion on where they actually belong 🙂 |
di
approved these changes
May 1, 2023
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.
This adds an "Internals and Technical Details" page with both a high-level description of how trusted publishing works and a Q&A section with some pre-filled Q&As on the design of trusted publishing.
Closes #13470.
CC @di