Repository navigation
chore(context7): add the ownership claim to context7.json - #100
Merged
Merged
Conversation
Context7 verifies a library claim by reading url and public_key from the root context7.json on the default branch. Add both to the existing file rather than replacing it with the claim modal's two-field snippet, which would drop the folder whitelist and re-index context/ and .claude/ on the next refresh. context/stack.md records the claim fields and drops the sentence saying the Context7 listing is not tracked here, which this change makes untrue.
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
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.
What
Adds Context7's ownership-claim fields to the existing root
context7.json, so the maintainer can claim/northguild/worktreeon context7.com:Context7 verifies a claim by reading these two fields from
context7.jsonon the default branch.public_keyis a public verification key and is meant to be committed.The claim modal suggests a file containing only these two fields. This PR adds them to the existing file instead. Replacing the file would drop the folder whitelist from #99, and the next refresh would index
context/and.claude/. No existing field changed: thecontext7.jsondiff is one comma and two new lines. Context7's schema lists both keys, so the file still passes itsadditionalProperties: falserule.context/stack.mdgains a short paragraph saying the file holds the claim and what breaks if the fields are changed or the file is replaced. It also drops the sentence "Whether the repository has been submitted to Context7 is not tracked here", which this change makes untrue.No release note
context/**owes none percontext/release.md. Rootcontext7.jsonhas no row there and isn't in the package'sfileslist. The release-note check's path filter doesn't match either file.Verification
pnpm check: exit 0. This is a docs/config-only change, so percontext/verify.mdGate 1 is lint plus a read of the diff. I also checked that the JSON parses, that no existing key differs fromorigin/main, and that both values match the claim modal.After merge
In the claim modal at https://context7.com/northguild/worktree/admin, choose context7.json as the parsing-config source, then click Claim Library.