mirror of
https://github.com/supabase/supabase.git
synced 2026-06-18 13:43:53 +08:00
9c03ad6b02
## What kind of change does this PR introduce? Docs update. Related to DEPR-551. ## What is the current behavior? Docs MDX still uses the legacy `label` prop for Admonitions, even though #45618 added `title` and kept `label` only as a backwards-compatible alias after #45302 was reverted in #45535. ## What is the new behavior? Migrates Docs-owned Admonitions from `label=` to `title=` without changing rendered copy, component APIs, Studio callsites, design-system examples, or the legacy `label` alias. <!-- This is an auto-generated comment: release notes by coderabbit.ai --> ## Summary by CodeRabbit * **Documentation** * Standardized admonition headings across the docs by switching how admonition headings are provided (preserving all visible guidance and examples). Content and instructions remain unchanged; this ensures consistent rendering of callouts and improves uniformity across guides and reference pages. <!-- review_stack_entry_start --> [](https://app.coderabbit.ai/change-stack/supabase/supabase/pull/46053?utm_source=github_walkthrough&utm_medium=github&utm_campaign=change_stack) <!-- review_stack_entry_end --> <!-- end of auto-generated comment: release notes by coderabbit.ai --> --------- Co-authored-by: Chris Chinchilla <chris.ward@supabase.io>
31 lines
1.7 KiB
Plaintext
31 lines
1.7 KiB
Plaintext
---
|
|
title: 'Integrations'
|
|
description: 'Use Supabase branching with hosting providers and other tools.'
|
|
subtitle: 'Use Supabase branching with hosting providers and other tools'
|
|
---
|
|
|
|
Branching works with hosting providers that support preview deployments. Learn how to integrate Supabase branching with various platforms and tools.
|
|
|
|
## Hosting providers
|
|
|
|
With the Supabase branching integration, you can sync the Git branch used by the hosting provider with the corresponding Supabase preview branch. This means that the preview deployment built by your hosting provider is matched to the correct database schema, edge functions, and other Supabase configurations.
|
|
|
|
### Vercel
|
|
|
|
Install the Vercel integration:
|
|
|
|
- From the [Vercel marketplace](https://vercel.com/integrations/supabase) or
|
|
- By clicking the blue `Deploy` button in a Supabase example app's `README` file
|
|
|
|
<Admonition type="note" title="Vercel GitHub integration also required.">
|
|
|
|
For branching to work with Vercel, you also need the [Vercel GitHub integration](https://vercel.com/docs/deployments/git/vercel-for-github).
|
|
|
|
</Admonition>
|
|
|
|
And make sure you have [connected](/dashboard/org/_/integrations) your Supabase project to your Vercel project.
|
|
|
|
Supabase automatically updates your Vercel project with the correct environment variables for the corresponding preview branches. The synchronization happens at the time of Pull Request being opened, not at the time of branch creation.
|
|
|
|
As branching integration is tied to the Preview Deployments feature in Vercel, there are possible race conditions between Supabase setting correct variables, and Vercel running a deployment process. Because of that, Supabase is always automatically re-deploying the most recent deployment of the given pull request.
|