You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Docusaurus BetaBadge swapped for the Mintlify snippet component.
Internal links rewritten from /cloud/managed-postgres/... to /products/managed-postgres/... to match the convention used elsewhere in this repo.
sidebars.js and styles/ClickHouse/Headings.yml from the source PR don't apply here (Mintlify uses navigation.json; there's no Vale config in this repo).
Ambiguity
The branching doc links to /cloud/managed-postgres/local-development, but docs/cloud/managed-postgres/local-development.md hasn't been ported to Mintlify yet. The link text is preserved as plain text with a TODO comment so it can be wired up once that page lands.
Note
Low Risk
Documentation and navigation only; no product code or security-sensitive behavior changes.
Overview
Adds a new Managed Postgres branching guide (branching.mdx) that documents PITR-based branches as independent deployments: how creation works, use cases, sizing, recovery time expectations, and guidance to prefer local dev over prod-derived branches for day-to-day work. The page uses the Mintlify BetaBadge snippet and links to backup/restore and local development under /products/managed-postgres/....
The migrations overview gains a Migrating from Supabase section pointing to an external step-by-step guide on GitHub. Navigation lists branching in Features immediately after backup-and-restore.
Reviewed by Cursor Bugbot for commit 8d2ec92. Bugbot is set up for automated code reviews on this repo. Configure here.
@copilot please resolve the TODO comment, i've merged the local-development changes, so you just need to merge main into this branch and update the TODO:
The branching doc links to /cloud/managed-postgres/local-development, but docs/cloud/managed-postgres/local- development.md hasn't been ported to Mintlify yet. The link text is preserved as plain text with a TODO comment so it can be wired up once that page lands.
@copilot please resolve the TODO comment, i've merged the local-development changes, so you just need to merge main into this branch and update the TODO:
The branching doc links to /cloud/manage...
Done — merged main (which brought in products/managed-postgres/local-development.mdx) and replaced the plain-text + TODO comment with a live link: [Local development environments](/products/managed-postgres/local-development). See commit docs: resolve TODO - wire up local-development link in branching.mdx.
Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You have signed the CLA already but the status is still pending? Let us recheck it.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Ports ClickHouse/clickhouse-docs#6347 — adds Managed Postgres branching (PITR) doc and a Supabase migration pointer.
Changes
products/managed-postgres/branching.mdx(new PITR/branching guide).products/managed-postgres/migrations/overview.mdxlinking to the external migration gist.branchingafterbackup-and-restoreinproducts/managed-postgres/navigation.json.Context
/cloud/managed-postgres/branching,/cloud/managed-postgres/migrations/overview).BetaBadgeswapped for the Mintlify snippet component./cloud/managed-postgres/...to/products/managed-postgres/...to match the convention used elsewhere in this repo.sidebars.jsandstyles/ClickHouse/Headings.ymlfrom the source PR don't apply here (Mintlify usesnavigation.json; there's no Vale config in this repo).Ambiguity
The branching doc links to
/cloud/managed-postgres/local-development, butdocs/cloud/managed-postgres/local-development.mdhasn't been ported to Mintlify yet. The link text is preserved as plain text with aTODOcomment so it can be wired up once that page lands.Note
Low Risk
Documentation and navigation only; no product code or security-sensitive behavior changes.
Overview
Adds a new Managed Postgres branching guide (
branching.mdx) that documents PITR-based branches as independent deployments: how creation works, use cases, sizing, recovery time expectations, and guidance to prefer local dev over prod-derived branches for day-to-day work. The page uses the MintlifyBetaBadgesnippet and links to backup/restore and local development under/products/managed-postgres/....The migrations overview gains a Migrating from Supabase section pointing to an external step-by-step guide on GitHub. Navigation lists
branchingin Features immediately afterbackup-and-restore.Reviewed by Cursor Bugbot for commit 8d2ec92. Bugbot is set up for automated code reviews on this repo. Configure here.