style: apply /style-guide pass to models/runs#2724
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
|
📚 Mintlify Preview Links📝 Changed (21 total)📄 Pages (21)
🤖 Generated automatically when Mintlify deployment succeeds |
🔗 Link Checker Results✅ All links are valid! No broken links were detected. Checked against: https://wb-21fd5541-style-guide-models-runs-20260604-113608.mintlify.app |
890eaac to
765929f
Compare
765929f to
1df3e6e
Compare
There was a problem hiding this comment.
Pull request overview
This PR applies an automated style-guide pass across the models/runs documentation set, primarily standardizing wording, placeholders, and adding frontmatter keywords to improve search/discoverability.
Changes:
- Added/updated frontmatter metadata (
keywords) and standardized placeholder formats (for example[ENTITY],[PROJECT],[RUN-ID]). - Refined headings, lists, and procedural steps for consistency with the style guide.
- Introduced some new/updated cross-references and URL templates within the runs documentation.
Reviewed changes
Copilot reviewed 20 out of 20 changed files in this pull request and generated 14 comments.
Show a summary per file
| File | Description |
|---|---|
| models/runs/alert.mdx | Style/wording updates and added keywords for scriptable alerts documentation. |
| models/runs/color-code-runs.mdx | Reorganized/clarified key-based colors instructions; added keywords. |
| models/runs/compare-runs.mdx | Wording and accessibility text adjustments for baseline/pinned run comparison docs. |
| models/runs/customize-run-display.mdx | Expanded procedural clarity for runs table customization; added keywords. |
| models/runs/delete-runs.mdx | Clarified deletion behavior/retention wording; added keywords. |
| models/runs/filter-runs.mdx | Reworded filter instructions/operators table; added keywords. |
| models/runs/forking.mdx | Style updates and expanded explanations; added keywords. |
| models/runs/grouping.mdx | Wording/step formatting updates for grouping/job type; added keywords. |
| models/runs/infrastructure-alerts.mdx | Improved prerequisite wording and formatting; added keywords. |
| models/runs/initialize-run.mdx | Expanded guidance for reinit / multiple runs; added keywords. |
| models/runs/manage-runs.mdx | Clarified run move workflow and outcomes; added keywords. |
| models/runs/resuming.mdx | Updated wording and placeholders for resume behaviors; added keywords. |
| models/runs/rewind.mdx | Clarified rewind limitations/workflow; added keywords. |
| models/runs/run-colors.mdx | Style updates for run color customization/randomize/reset guidance; added keywords. |
| models/runs/run-identifiers.mdx | Updated placeholders and expanded explanations for run IDs/names; added keywords. |
| models/runs/run-states.mdx | Wording/formatting updates for run state definitions and viewing states; added keywords. |
| models/runs/search-runs.mdx | Clarified search/regex toggle procedure; added keywords. |
| models/runs/stop-runs.mdx | Expanded stop-run guidance and added keywords. |
| models/runs/tags.mdx | Clarified tagging workflows across SDK/API/UI and added keywords. |
| models/runs/view-logged-runs.mdx | Expanded run-inspection guidance and improved alt text; added keywords. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Fix broken in-page anchors, code samples, and wording flagged in PR review: - run-identifiers: drop dead #autogenerated-run-ids link; point Overview link to view-logged-runs#overview; add /runs/ to the run URL template; remove spaces around the kwarg = in api.run() - forking: retarget #unique-run-identifiers link to #run-id - rewind: retarget Overview tab link to view-logged-runs#overview - resuming: add id="[RUN-ID]" to the resume="must" example; retarget custom run ID link to run-identifiers#create-a-custom-run-id - initialize-run: call wandb.setup() instead of using it as a context manager; fix nested with-block indentation - filter-runs: fix anchor to #example-filter-runs-with-tags; "works" -> "work" - compare-runs: underperforms is "directionally worse than" the baseline - stop-runs: capitalize Running to match run-states Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
models/runs.mdx linked to #unique-run-identifiers (x2) and #autogenerated-run-ids, neither of which exists on the run-identifiers page. Point all three to #run-id (the ## Run ID heading). The #run-name link was already valid and is unchanged. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Resolve conflict in models/runs/compare-runs.mdx: keep main's pin-limit feature (20/19), the new 'Compare runs across projects' section, and the heading restructure, layered with the style-pass edits (keywords frontmatter, section lead-ins, the 'directionally worse than' fix, and sequential list numbering). Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The automated /style-guide pass added keywords: frontmatter to each page. Per reviewer preference (auto-generated keywords are noise), back them out across all 20 models/runs pages. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Summary
This PR applies the
/style-guideskill (Google Developer Style Guide + CoreWeave conventions) to 20 files inmodels/runs. The run was automated; no technical content was intentionally changed.Files edited
models/runs/alert.mdxmodels/runs/color-code-runs.mdxmodels/runs/compare-runs.mdxmodels/runs/customize-run-display.mdxmodels/runs/delete-runs.mdxmodels/runs/filter-runs.mdxmodels/runs/forking.mdxmodels/runs/grouping.mdxmodels/runs/infrastructure-alerts.mdxmodels/runs/initialize-run.mdxmodels/runs/manage-runs.mdxmodels/runs/resuming.mdxmodels/runs/rewind.mdxmodels/runs/run-colors.mdxmodels/runs/run-identifiers.mdxmodels/runs/run-states.mdxmodels/runs/search-runs.mdxmodels/runs/stop-runs.mdxmodels/runs/tags.mdxmodels/runs/view-logged-runs.mdxRecommendations for technical review
Prerequisites
alert.mdxlisting requiredwandbSDK version, W&B account, and Slack workspace permissions needed to authorize the W&B Slack app.delete-runs.mdx: document required permissions for deleting runs (project admin, member, team-level role) in the W&B App procedure, and consider linking to API authentication setup for the Python tab.infrastructure-alerts.mdx: define what constitutes a "supported CKS cluster" (region, node type, GPU model, Mission Control enablement) and document the enablement path (automatic, admin toggle, CoreWeave-side configuration, or Preview gating).initialize-run.mdx: link install/upgrade instructions for thev0.19.10+ requirement called out in the Requirements note.manage-runs.mdx: clarify which role/permission grants the "access to the run at its current and new locations" required to move runs across teams.resuming.mdx: verify the relative anchor link./#custom-run-ids(line 102) resolves to the intended section.rewind.mdx: add guidance on how to check or upgrade the installed SDK version for the>=0.17.1requirement.run-identifiers.mdx: consider stating that readers must have the SDK installed and an active W&B account before the SDK examples.view-logged-runs.mdx: note any minimum CLI version or install/setup link forwandb beta leet; clarify whether code logging is opt-in (e.g.,wandb.Run.log_code()); link to per-run Git enablement instructions.Verification steps
alert.mdx: add a minimal, always-fires example for end-to-end verification ofrun.alert(), and add troubleshooting guidance for "I enabled alerts but nothing arrives."color-code-runs.mdx: consider whether a brief description of the workspace immediately after enabling key-based colors would help readers confirm success.customize-run-display.mdx: add confirmation sentences after the Add columns procedure (steps 3 and 5) and after the Sort runs procedure.delete-runs.mdx: add verification guidance after the UI procedure and a verification command after the Python loop.initialize-run.mdx: add sample output or a workspace screenshot for the multi-run/concurrent example.infrastructure-alerts.mdx: add a short "what you'll see" subsection (annotated run plot, alert types, workspace location).manage-runs.mdx: add a verification cue for successful run moves across teams/projects.resuming.mdx: add guidance for confirming a run actually resumed (UI cue or stdout).rewind.mdx: consider adding a verification step after each rewind code example.run-identifiers.mdx: add expected-outcome text after each procedure (custom run ID/name, rename a run, rename display name).run-states.mdx: add a short sample output block to the Python SDK example.search-runs.mdx: add an expected-outcome sentence after a successful search and after disabling RegEx.stop-runs.mdx: state the resulting run state in the Python SDK tab so it parallels the W&B App tab.view-logged-runs.mdx: add an "On success, LEET opens with…" sentence; add an outcome sentence at the end of the W&B App procedure.Technical accuracy
alert.mdx: confirmwait_duration=300units and that 300s matches the "no more than once every 5 minutes" claim; document the full set ofAlertLevelvalues and per-level delivery/formatting behavior; verify Slack mention syntax<@U1234ABCD>and clarify behavior in email; confirm thewandb.ai/teams/[YOUR-TEAM]path and the alert types configurable on team settings; confirm Dedicated Cloud coverage for the Multi-tenant Cloud caveat.color-code-runs.mdx: verify the Latest description phrasing versus Max/Min; confirm UI casing of Latest; verify the Key dropdown displays"Accuracy"vs."acc"; confirm the exact Buckets UI label; verify the screenshot's correct bucket placement for accuracy 0.8232 (Bucket 5 vs. Bucket 6); confirm new alt-text matches the screenshots.compare-runs.mdx(line 108): the parenthetical defining "underperforms" currently duplicates "outperforms" — should read "(is directionally worse than) the baseline".customize-run-display.mdx: confirm both alternative paths for pinning/unpinning columns are valid; confirm whether the Note on lines 68-70 duplicates the section intro; confirm the 1,000-run display limit in the commented-out note on lines 7-9; clarify whether Show latest appears only for aggregated/metric columns.delete-runs.mdx: verify the "starting a new run with a deleted run's ID fails with an error" claim across UI/API and Cloud/Self-Managed; verify the Warning callout against the actual UI flow (Registry-specific confirm prompt); verify the Mermaid flowchart's Registry warning branch and "Production aliases affected" detail; confirmGORILLA_DATA_RETENTION_PERIODis current and documented; confirm "W&B" as the actor in line 17; consider precision for "background jobs catch up"; verify the "Public API" reference indescription/keywords; reconcile "self-managed deployments" vs. "W&B Self-Managed" usage.filter-runs.mdx: verify the literal UI string for**Show only my works**(likely "Show only my work" or "Show only my runs"); confirm whether steps 3 and 4 of the Tags example are distinct or merged in error; normalize**New Filter**vs.**New filter**casing; confirm operator casing in the table (is/is notvs.IN/NOT IN); reconcilestate = "finished"vs.State = finishedvalue rendering; confirm whether the close affordance is a literalxglyph.forking.mdx: confirm the Warning's "active development and in private preview" status; verify thewandbSDK0.16.5+ minimum; confirm the live demo link still resolves and is appropriate.grouping.mdx: verify the "Organize runs into groups" step ordering (lines 55-63); clarify whether step 4 of "Remove runs from a group" removes runs or deletes the group; clarify whether "select a Group" means a literal label or a specific group name; reconcile "Move runs between groups" with "Move to group"; verifywandb.Run.groupandwandb.Run.job_typeas the current public SDK property names; confirm that removing all runs auto-deletes the group; clarify whether grouping is mutable via SDK afterwandb.init().infrastructure-alerts.mdx: confirm0.20.1as the minimum SDK version; confirm0.73.0as the minimum W&B Server version and the exactSERVER_FLAG_ENABLE_CORE_WEAVE_OBSERVABILITYenv var name (includingCORE_WEAVEvs.COREWEAVEcasing); verify the three runtime behaviors on lines 25-27 are accurate and complete.initialize-run.mdx: confirmwandb.setup()is a context manager that bindsruncorrectly; fix theevaluate_loss_accuracyreturn annotation-> (float, float)to valid typing syntax (tuple[float, float]); reconcile concurrent-example variable names (run_a/run_b1vs.tracking_run); confirm the 6-space indentation in the innerwith wandb.init()block is intentional.manage-runs.mdx: verify runs are truly removed from the original project (no tombstone/redirect); confirmwandb artifact get/putandApi.artifactare still recommended for artifact migration; confirm whether moving a run preserves run history, system metrics, logged media, and tags; decide whether the title should be pluralized; name the destination team/project dropdown explicitly; verify the Move to project button label.resuming.mdx: the first resume procedure's code is missing theid="[RUN-ID]"argument expected by the prose; verify the "~5-minute crash detection window" on line 122; confirm whether W&B's agent specifically expects128 + signumexit codes; verify thatwandb.agent()runs the training function in a thread; confirm sweep agents drain the run queue before generating new combinations; normalize the Markdown separator row mixing---and--.rewind.mdx: enumerate the "known performance limitations with rewind"; confirm the private preview status andsupport@wandb.comcontact are current; confirm whetherentityandprojectinwandb.init()must match the original run forresume_from; confirm tense changes "produces" → "produced" and "created" → "creates" still describe runtime behavior accurately.run-colors.mdx: confirm that hovering over the Name column header is required to surface the action menu (vs. visible by default); verify the randomize gating depends only on sort/filter/search/group modifications and not also on minimum run count.run-identifiers.mdx: verify theentity="[ENTITY]"placeholder inCreate a custom run ID(the original usedentity="<project>", which appears to be a typo); confirm the same parameter labeling inCreate a custom run name; confirm the/images/runs/unique-run-id.pngimage is accurate for both run ID and run name sections (or split into two images); confirmapi.run(path = "...")spacing matches project Python style.run-states.mdx: confirmPendingis exposed exactly asPending(capitalized) viarun.statefrom the Python SDK.search-runs.mdx: confirm the inactive RegEx toggle has a non-color visual cue (dimmed icon, unfilled state) so the new "appears inactive" wording matches actual UI.stop-runs.mdx: verify the casing of state labels ("fromrunningtoKilled") in the W&B App and align with/models/runs/run-states.tags.mdx: confirm whetherwandb.Run.tagsis a tuple, a list, or both, and align the prose with the example that uses.append(); confirm the + icon and x affordance still match the current UI.view-logged-runs.mdx: verify the nested-config search workaround (whether dot-notation or another pattern works); confirm Command and Python executable are meaningfully distinct fields; verify all new alt-text matches the screenshots; confirm marketing-style claims about Tracked Hours, Runtime, and Git state are still accurate.Missing content
alert.mdx: add a reference table forrun.alert()parameters (title,text,level,wait_duration); explainAlertLevelenum members and per-level behavior; clarify whether@mentions work in email or only in Slack.color-code-runs.mdx: consider whether theExample: key-based colors with a loss metricsection should move after the explanatory subsections for better IA.compare-runs.mdx: resolve the stale{/* TODO screenshot */}author marker on line 213; consider whether steps 2 and 3 of the example workflow (lines 144-211) need confirmation sentences; verify thePinRunsCondensedsnippet provides any "why" framing needed; clarify standard W&B terms (run selector, runs table, workspace, run set) inline or via cross-reference; consolidate or confirm the repeated "lines for the baseline run appear bolder" sentence (lines 40, 84, 90); review 2-space vs. 4-space nested list indentation on lines 209-210.customize-run-display.mdx: clarify whether the Hide columns "View all hidden columns" line belongs there, in Add columns, or in its own subsection.delete-runs.mdx: document bulk-deletion limits, behavior for sweep/group runs and runs with active alerts, whetherrun.delete()is reversible, and behavior in team/org-locked projects; note any support-side recovery path for the "Cannot be recovered" flowchart node.filter-runs.mdx: add Prerequisites/permissions section; document default filter persistence across sessions/projects/views; fix the broken anchor link#filter-runs-with-tags(target generates#example-filter-runs-with-tags); decide whether to restore or remove the commented-out sections (lines 93-132); fix the "AND OR conditions" frontmatter keyword.forking.mdx: align the example script comment with the loop's actual range; harmonize thefork_step = int("[NUM]")vs.fork_step = 200placeholder pattern; consider whether the<Tip>after the second code block duplicates the preceding paragraph.grouping.mdx: add prose explaining what to replace[ENTITY]and[PROJECT]with before each code block; decide whether to restore or remove the commented-outWANDB_RUN_GROUP/wandb.util.generate_id()block.infrastructure-alerts.mdx: link to where/how to set env vars on the W&B app pod for the Self-Managed instructions.initialize-run.mdx: fill in the empty "Example use case" cell forreturn_previousin thereinittable; add a header to the first column of thereinittable; consider a brief note onreinitinteraction withwandb.finish()in notebooks; consider renaming theExample: Concurrent processesheading to a noun phrase.manage-runs.mdx: decide whether to restore or remove the large commented-out "Move runs to a group" and "Manage runs in bulk" sections; document what happens to references from Reports, Sweeps, or Artifacts when a run moves; document whether the move is reversible.resuming.mdx: fill in the empty "Use case" cell for the"never"row in the resume-behavior table; show how the preemption signal is delivered in non-SLURM environments; normalize placeholder style (bracketed vs. literal paths).rewind.mdx: review the commented-out block at lines 27-30 referring to "Run archiving"; define what an "archived resumption" is in concrete terms.run-colors.mdx: remove or relocate the stale{/* … */}comment on line 35 that duplicates the visible Note.run-identifiers.mdx: fix the broken anchor#autogenerated-run-ids(line 11) and#overview-tab(line 82); clarify which page/view (Workspace tab vs. Runs tab) the "action menu at the top of the list of runs" refers to; decide whether to restore or remove the commented-out<Tabs>block describing renaming runs from a report.run-states.mdx: consider adding a brief note on state transitions (e.g.,Crashed→Finishedafter resync,Killedvs.Failed).search-runs.mdx: consider linking "Runs table" and "Workspace" in the intro to their concept pages.stop-runs.mdx: consider noting whetherCtrl+Dis the only SDK stop signal across platforms (macOS terminals, Jupyter notebooks, IDEs).tags.mdx: document SDK/Public API tag removal for parity with the "Add tags" coverage.view-logged-runs.mdx: normalize UI label casing (Title Case vs. sentence case) across Overview fields; consider whether the in-page anchor links in the intro sentence (line 27) add value.How to review