Draft improvements from assistant conversations: run moves and nested config#2830
Open
mintlify[bot] wants to merge 1 commit into
Open
Draft improvements from assistant conversations: run moves and nested config#2830mintlify[bot] wants to merge 1 commit into
mintlify[bot] wants to merge 1 commit into
Conversation
Contributor
Author
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
Contributor
📚 Mintlify Preview Links📝 Changed (2 total)📄 Pages (2)
🤖 Generated automatically when Mintlify deployment succeeds |
Contributor
🔗 Link Checker Results✅ All links are valid! No broken links were detected. Checked against: https://wb-21fd5541-mintlify-8476678c.mintlify.app |
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.
Summary
Closes two recurring documentation gaps surfaced by recent assistant conversation buckets: users repeatedly ask whether runs can be moved programmatically, and how to put a nested dictionary into
wandb.config.Changes
models/runs/manage-runs.mdx: state explicitly that moving runs is UI-only with no SDK or Public API equivalent, that copying runs is not supported, and point toRun.delete()as the one run-management call available from the Public API.models/track/config.mdx: add a "Nested dictionaries in config" subsection explaining thatconfig-defaults.yaml(desc/value) does not support nested dicts inline, showing the Pythonwandb.init(config=...)pattern, and noting that W&B flattens nested keys with dots in the UI and Public API filters.Context
Recent assistant traffic shows repeated questions like "are there API endpoints to move runs", "are there programmatic ways to move runs", and YAML/config questions where users tried to encode nested dicts in
config-defaults.yaml. The existing pages described the supported paths but did not call out the unsupported ones, so the assistant had to infer the negative answer each time.