Skip to content

feat(studio): refine pipeline creation copy - #50751

Draft
dnywh wants to merge 1 commit into
dnywh/studio/improve-snowflake-formfrom
dnywh/studio/refine-pipeline-form-copy
Draft

dnywh wants to merge 1 commit into
dnywh/studio/improve-snowflake-formfrom
dnywh/studio/refine-pipeline-form-copy

Conversation

@dnywh

@dnywh dnywh commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

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

  1. Open Database > Replication and click Add pipeline.
  2. Switch between destination types and confirm the pipeline-name example, destination summary, and field descriptions update appropriately.
  3. Open Advanced settings and confirm the batch wait-time default is shown in the description while the input placeholder is 10000.
  4. Select each supported destination and confirm Docs opens its matching destination guide.
  5. Select ClickHouse and confirm the engine choices read ReplacingMergeTree and MergeTree.

Checklist

  • I have read CONTRIBUTING.md
  • If I wrote a new docs topic or edited an existing topic, I used the /write-the-docs or /edit-the-docs skill, which references WORD_LIST and the docs CONTRIBUTING guide

Use destination-specific examples, clearer field descriptions, concise advanced-setting guidance, and destination-aware documentation links throughout the creation sheet.
@vercel

vercel Bot commented Sep 22, 2026

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
studio-self-hosted Ready Ready Preview Sep 22, 2026 7:12pm UTC
studio-staging Ready Ready Preview Sep 22, 2026 7:12pm UTC
6 Skipped Deployments
Project Deployment Actions Updated
studio Ignored Ignored Sep 22, 2026 7:12pm UTC
design-system Skipped Skipped Sep 22, 2026 7:12pm UTC
docs Skipped Skipped v0 Sep 22, 2026 7:12pm UTC
kb Skipped Skipped Sep 22, 2026 7:12pm UTC
ui-library Skipped Skipped Sep 22, 2026 7:12pm UTC
zone-www-dot-com Skipped Skipped v0 Sep 22, 2026 7:12pm UTC

Request Review

@coderabbitai

coderabbitai Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

Important

Draft PR not reviewed

Draft PRs are not automatically reviewed by default.

  • Trigger a manual review

To automatically review draft PRs, update your CodeRabbit configuration:

reviews:
  auto_review:
    drafts: true

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.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

@supabase

supabase Bot commented Sep 22, 2026

Copy link
Copy Markdown

This pull request has been ignored for the connected project xguihxuzqibwxjnimxev because there are no changes detected in supabase directory. You can change this behaviour in Project Integrations Settings ↗︎.


Preview Branches by Supabase.
Learn more about Supabase Branching ↗︎.

@github-actions

github-actions Bot commented Sep 22, 2026

Copy link
Copy Markdown
Contributor

🎭 Playwright Test Results (tanstack)

passed  250 passed
flaky  1 flaky
skipped  5 skipped

Details

stats  256 tests across 30 suites
duration  6 minutes, 35 seconds
commit  1b63b02

Flaky tests

Features › queue-table-operations.spec.ts › Queue Table Operations › mixed operations (add, edit, delete) can be batched

Skipped tests

Features › auth-users.spec.ts › should show web3 users as enabled when the matching web3 provider is enabled
Features › sql-editor.spec.ts › SQL Editor › snippet favourite works as expected
Features › sql-editor.spec.ts › SQL Editor › share with team works as expected
Features › sql-editor.spec.ts › SQL Editor › folders works as expected
Features › sql-editor.spec.ts › SQL Editor › other SQL snippets actions work as expected

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant