chore(context7): drop the stale planning/ exclusion - #169
Merged
Conversation
planning/ was removed by this repo's migration off that convention, so the exclusion has been a no-op since; it was left in place because it sat outside the migration recipe's scope. Dropping the key rather than leaving an empty list: Context7's schema (https://context7.com/schema/context7.json) declares no required properties and gives excludeFolders a default of [], so an absent key and an empty list are equivalent. Absent matches the repos that never carried the line.
Benchmark gate✅ gate passed
Gated (fails the build): |
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
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.
context7.jsonexcludes aplanning/directory that no longer exists. This repo migrated off theplanning/convention, and the exclusion has been a dead entry since — it was left behind because it sat outside that migration's recipe, so removing it is an independent call rather than migration fallout. Part of the cleanup around modern-python/.github#67.Why drop the key rather than leave an empty list
Checked against Context7's published schema (https://context7.com/schema/context7.json) rather than assumed:
requiredarray, so every property is optional;excludeFolderscarries"default": []and nominItems.An absent key and
[]are therefore equivalent to Context7. Absent is what the repos that never carried the line already look like (eof-fixer,faststream-concurrent-aiokafka), so dropping it converges the org on one shape.Non-goals
No other exclusion is touched — this repo excluded only
planning, so there is no partial-list edit. Indexing behaviour is unchanged, since the excluded path does not exist.Verification
git ls-tree -d origin/main planningreturns nothing: the directory is genuinely absent atmain, not merely absent from the working tree.just lint-ciclean.