Clarify API key requirement for docs updates #68
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
This PR adds a short clarification to the README about when a Talent Protocol API key is actually required. - Makes it clear that contributors editing only non-autogenerated `.mdx` docs can run `npm run start` without needing an API key. - Aims to reduce friction for first-time contributors who just want to fix or add simple documentation.
Author
|
Just checking in. If you’d like any changes, let me know! |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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 PR adds a short clarification to the README about when a Talent Protocol API key is actually required.
.mdxdocs can runnpm run startwithout needing a Talent Protocol API key.