Repository navigation
docs: correct config discovery boundary - #45681
Merged
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
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.
Why
The shipped OpenCode skill and its linked configuration guide say project config discovery stops at the project root. The loader intentionally walks every ancestor through the filesystem root, and an existing Core test preserves configuration found above the detected project boundary.
What Changes
.opencodefiles.Scope
This corrects CONTRIBUTOR-01 in the built-in skill and companion public guide only. It does not change Config discovery, watcher behavior, opt-outs, source precedence, or the separate instruction-discovery boundary.
Verification
All checks passed. The website build completed link validation, and the repository-wide typecheck completed all 33 tasks.