Conversation
Use destination-specific examples, clearer field descriptions, concise advanced-setting guidance, and destination-aware documentation links throughout the creation sheet.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
6 Skipped Deployments
|
|
Important Draft PR not reviewedDraft PRs are not automatically reviewed by default.
To automatically review draft PRs, update your CodeRabbit configuration: reviews:
auto_review:
drafts: trueThanks 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 |
|
This pull request has been ignored for the connected project Preview Branches by Supabase. |
🎭 Playwright Test Results (tanstack)Details
Flaky testsFeatures › queue-table-operations.spec.ts › Queue Table Operations › mixed operations (add, edit, delete) can be batched Skipped testsFeatures › auth-users.spec.ts › should show web3 users as enabled when the matching web3 provider is enabled |
Problem
The pipeline creation sheet uses generic examples, inconsistent destination terminology, and Advanced settings copy that does not explain what is being overridden. Its Docs button also sends most destinations to the general Pipelines guide.
This PR is stacked on #50719 so the shared copy builds on the focused Snowflake field improvements.
Solution
Adds destination-specific pipeline-name examples and field descriptions, clarifies destination summaries and Advanced settings, uses human-readable ClickHouse engine names, shortens the primary action to Start pipeline, and links the Docs button to the selected destination guide.
To test
Review instructions
10000.Checklist
/write-the-docsor/edit-the-docsskill, which references WORD_LIST and the docs CONTRIBUTING guide