docs(provenance): make the provenance details easier to consume #614
Conversation
This file contains 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
travi
reviewed
May 9, 2023
travi
requested changes
May 9, 2023
Co-authored-by: Matt Travi <github@travi.org>
|
Should be fixed now. |
travi
approved these changes
May 9, 2023
travi
changed the title
|
🎉 This PR is included in version 10.0.4 🎉 The release is available on: Your semantic-release bot 📦🚀 |
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.
What
Extending the npm provenance section to be more helpful and provide complete example.
Why
CI/CD pipeline failed and required digging into the issue log to find out other permissions are also needed to release a GitHub version, etc.
The change
Updates the npm provenance section with copy/paste working example of YAML code that helps developers not fall into missing permission problems when wanting to enable the feature.