Add namespace section in import-landscapes#6
Merged
Conversation
VictorLeach96
approved these changes
Mar 24, 2026
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.
Adds
namespace optionin import-landscapes page underpruneNote
Low Risk
Documentation-only change describing how
namespacescopesprune=truedeletions; no code paths or runtime behavior are modified.Overview
Adds a new Namespace option section to the landscape import guide explaining how to set
namespacein YAML/JSON and how it interacts withprune=trueto limit deletions to the same import source, with example request snippets.Written by Cursor Bugbot for commit ca1e948. This will update automatically on new commits. Configure here.