fix: Fix all links in repo README and associated VSCode Marketplace listing - #2066
fix: Fix all links in repo README and associated VSCode Marketplace listing#2066arora-saurabh448 wants to merge 4 commits into
Conversation
…isting to point to help.altimate.ai
WalkthroughThe README now uses ChangesREADME documentation links
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
This incremental change appends the same UTM tracking query string ( Previous Review Summary (commit 555046c)Current summary above is authoritative. Previous snapshots are kept for context only. Previous review (commit 555046c)Status: No Issues Found | Recommendation: Merge Files Reviewed (1 file)
This is a documentation-only change that migrates 13 documentation links from the old Reviewed by glm-5.2 · Input: 32.3K · Output: 6.9K · Cached: 241.3K Review guidance: REVIEW.md from base branch |
![coderabbitai[bot]](https://avatars.githubusercontent.com/in/347564?s=60&v=4){kind=small}
There was a problem hiding this comment.
Actionable comments posted: 3
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Around line 72-74: Update the “Compiled query preview and explanation”
description in the README to replace “as your write code” with “as you write
code,” leaving the rest of the text unchanged.
- Line 102: Update the documentation link in README.md to use the general Power
User FAQ destination for this generic “additional info” reference, or rename its
visible label to explicitly indicate “security FAQ” if the security-specific
destination must remain.
- Around line 50-52: Update the documentation link in the genmodel section to
point to the model-generation guidance covering both workflows: generating
models from sources and converting SQL into dbt models. Use separate links for
the source and SQL workflows, or replace the current destination with a page
that documents both, while preserving the surrounding description.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| ### <a id="genmodel"> Generate dbt™ Models from source or SQL</a> | ||
|
|
||
| Generate dbt™ models from sources defined in YAML. You can also convert existing SQL to a dbt™ model where references get populated automatically. [(docs)](https://docs.myaltimate.com/develop/clicktorun/) | ||
| Generate dbt™ models from sources defined in YAML. You can also convert existing SQL to a dbt™ model where references get populated automatically. [(docs)](https://help.altimate.ai/dbt-power-user/develop/clicktorun/) |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Link model-generation guidance to the model-generation pages.
The new destination is the “Click to build parent/child models” page. The Help Center has separate pages for generating models from sources and SQL, so this link opens a different feature page. (help.altimate.ai)
Use two links, or link to a page that documents both workflows.
Proposed fix
-Generate dbt™ models from sources defined in YAML. You can also convert existing SQL to a dbt™ model where references get populated automatically. [(docs)](https://help.altimate.ai/dbt-power-user/develop/clicktorun/)
+Generate dbt™ models from sources defined in YAML. [(source docs)](https://help.altimate.ai/dbt-power-user/develop/genmodelSource/) You can also convert existing SQL to a dbt™ model where references get populated automatically. [(SQL docs)](https://help.altimate.ai/dbt-power-user/develop/genmodelSQL/)📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### <a id="genmodel"> Generate dbt™ Models from source or SQL</a> | |
| Generate dbt™ models from sources defined in YAML. You can also convert existing SQL to a dbt™ model where references get populated automatically. [(docs)](https://docs.myaltimate.com/develop/clicktorun/) | |
| Generate dbt™ models from sources defined in YAML. You can also convert existing SQL to a dbt™ model where references get populated automatically. [(docs)](https://help.altimate.ai/dbt-power-user/develop/clicktorun/) | |
| ### <a id="genmodel"> Generate dbt™ Models from source or SQL</a> | |
| Generate dbt™ models from sources defined in YAML. [(source docs)](https://help.altimate.ai/dbt-power-user/develop/genmodelSource/) You can also convert existing SQL to a dbt™ model where references get populated automatically. [(SQL docs)](https://help.altimate.ai/dbt-power-user/develop/genmodelSQL/) |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` around lines 50 - 52, Update the documentation link in the
genmodel section to point to the model-generation guidance covering both
workflows: generating models from sources and converting SQL into dbt models.
Use separate links for the source and SQL workflows, or replace the current
destination with a page that documents both, while preserving the surrounding
description.
| ### <a id="queryexplanation"> Compiled query preview and explanation</a> | ||
|
|
||
| Get live preview of compiled query as your write code. Also, generate explanations for dbt™ code written previously (by somebody else). [(docs)](https://docs.myaltimate.com/develop/explanation/) | ||
| Get live preview of compiled query as your write code. Also, generate explanations for dbt™ code written previously (by somebody else). [(docs)](https://help.altimate.ai/dbt-power-user/develop/explanation/) |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Correct the grammar in the query explanation description.
Replace as your write code with as you write code.
Proposed fix
-Get live preview of compiled query as your write code.
+Get live preview of compiled query as you write code.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| ### <a id="queryexplanation"> Compiled query preview and explanation</a> | |
| Get live preview of compiled query as your write code. Also, generate explanations for dbt™ code written previously (by somebody else). [(docs)](https://docs.myaltimate.com/develop/explanation/) | |
| Get live preview of compiled query as your write code. Also, generate explanations for dbt™ code written previously (by somebody else). [(docs)](https://help.altimate.ai/dbt-power-user/develop/explanation/) | |
| ### <a id="queryexplanation"> Compiled query preview and explanation</a> | |
| Get live preview of compiled query as you write code. Also, generate explanations for dbt™ code written previously (by somebody else). [(docs)](https://help.altimate.ai/dbt-power-user/develop/explanation/) |
🧰 Tools
🪛 LanguageTool
[grammar] ~74-~74: Ensure spelling is correct
Context: ... Get live preview of compiled query as your write code. Also, generate explanations...
(QB_NEW_EN_ORTHOGRAPHY_ERROR_IDS_1)
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` around lines 72 - 74, Update the “Compiled query preview and
explanation” description in the README to replace “as your write code” with “as
you write code,” leaving the rest of the text unchanged.
Source: Linters/SAST tools
|  | ||
|
|
||
| Please check [documentation](https://docs.myaltimate.com/arch/faq/) for additional info. | ||
| Please check [documentation](https://help.altimate.ai/dbt-power-user/arch/faq/) for additional info. |
There was a problem hiding this comment.
🎯 Functional Correctness | 🟡 Minor | ⚡ Quick win
Use the general Power User FAQ for this generic link.
The current destination renders “Security FAQ”. The Help Center also has a separate “FAQ” page for common extension questions. Because this link is labeled as generic additional information, point it to the general FAQ or rename the link to “security FAQ”. (help.altimate.ai)
Proposed fix
-Please check [documentation](https://help.altimate.ai/dbt-power-user/arch/faq/) for additional info.
+Please check [the FAQ](https://help.altimate.ai/dbt-power-user/setup/faq/) for additional info.📝 Committable suggestion
‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.
| Please check [documentation](https://help.altimate.ai/dbt-power-user/arch/faq/) for additional info. | |
| Please check [the FAQ](https://help.altimate.ai/dbt-power-user/setup/faq/) for additional info. |
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` at line 102, Update the documentation link in README.md to use the
general Power User FAQ destination for this generic “additional info” reference,
or rename its visible label to explicitly indicate “security FAQ” if the
security-specific destination must remain.
Bundle Size Reportdarwin-arm64: 75.7 MB
linux-x64: 77.6 MB
win32-x64: 78.0 MB
|
The 13 doc links repointed in the previous commit land on help.altimate.ai with no attribution, so clicks from the extension are indistinguishable from organic docs traffic in PostHog. Uses the convention already in this README rather than a new one: the two support links carry `utm_source=dbt-power-user&utm_medium=marketplace`, so these match that source and medium exactly and add `utm_campaign=readme-docs` to separate doc links from the support links. A second source name for the same surface would split attribution in two. `utm_medium=marketplace` is kept even though this README also renders on GitHub — one file serves both surfaces, so they cannot be distinguished by UTM, and the existing links already made that call. Only URLs changed; no prose. The third-party docs.getdbt.com link is left alone. All 12 unique targets verified 200 with the params applied. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
There was a problem hiding this comment.
Actionable comments posted: 1
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 86: Update the SQL validator description in the README to replace
“columns no present in database” with “columns not present in the database,”
leaving the rest of the text unchanged.
🪄 Autofix
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
| ### <a id="validateSQL"> SQL validator</a> | ||
|
|
||
| Validate SQL to identify issues like mistyped keywords, extra parentheses, columns no present in database [(docs)](https://docs.myaltimate.com/test/sqlvalidation/) | ||
| Validate SQL to identify issues like mistyped keywords, extra parentheses, columns no present in database [(docs)](https://help.altimate.ai/dbt-power-user/test/sqlvalidation/?utm_source=dbt-power-user&utm_medium=marketplace&utm_campaign=readme-docs) |
There was a problem hiding this comment.
📐 Maintainability & Code Quality | 🟡 Minor | ⚡ Quick win
Correct the SQL validator description.
Replace columns no present in database with columns not present in the database.
🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
In `@README.md` at line 86, Update the SQL validator description in the README to
replace “columns no present in database” with “columns not present in the
database,” leaving the rest of the text unchanged.
2 participants
Fix all links in repo README and associated VSCode Marketplace listing to point to help.altimate.ai instead of old docs site. Redirects work fine, but domain authority for help.altimate.ai is taking a hit.
Summary by CodeRabbit