Conversation
✅ Deploy Preview for positron-posit-co ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
|
Looks like Snowflake URLs are failing for an unrelated page 👾 edit to add: that CI run seems to flake a lot on external URLs? |
There was a problem hiding this comment.
Pull request overview
Adds end-user documentation for Positron’s experimental Catalog Explorer feature and exposes the new page in both the Workbench and Positron documentation sidebars.
Changes:
- Added a new
catalog-explorer.qmdpage describing enabling the feature, adding/removing providers, and working with tables/files. - Added
catalog-explorer.qmdto the “Database Connections” sidebar section for both Workbench and Positron site configs.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| catalog-explorer.qmd | New documentation page for Catalog Explorer usage, commands, and settings. |
| _quarto-workbench.yml | Adds the Catalog Explorer page to the Workbench docs sidebar navigation. |
| _quarto-positron.yml | Adds the Catalog Explorer page to the Positron docs sidebar navigation. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| ::: {.callout-note} | ||
| Catalog Explorer is an experimental feature. Enable [`catalogExplorer.enabled`](positron://settings/catalogExplorer.enabled) in settings and restart Positron. | ||
| ::: |
There was a problem hiding this comment.
The setting key referenced here (catalogExplorer.enabled) appears inconsistent with the release notes in this repo, which refer to catalogExplorer.enable (e.g., release-notes/release-2025-11.qmd:39, release-notes/release-2025-12.qmd:42). Please confirm the correct setting name and update this link/text so users aren’t directed to a non-existent setting.
There was a problem hiding this comment.
it is in fact catalogExplorer.enabled, my apologies for not recognizing that for release notes 😬
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
You are entirely correct, but it does usually pass when run a second time. For now, we think the protection it gets us from stale links is worth re-running the CI when it is flaky. Maybe we should put the retries into the GH action itself. |
Co-authored-by: Julia Silge <julia.silge@gmail.com>
Addresses posit-dev/positron#11395