Skip to content

Commit 5daf672

Browse files
saltcodclaude
andauthored
chore: clarify GitHub integration copy (supabase#46286)
Light rewording of the "How does the GitHub integration work?" section on Integrations > GitHub Co-authored-by: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
1 parent 4668496 commit 5daf672

2 files changed

Lines changed: 4 additions & 4 deletions

File tree

apps/studio/components/interfaces/Settings/Integrations/GithubIntegration/GitHubIntegrationConnectionForm.tsx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -460,7 +460,7 @@ export const GitHubIntegrationConnectionForm = ({
460460
<FormItemLayout
461461
layout="flex-row-reverse"
462462
label="Deploy to production"
463-
description="Deploy changes to production on push including PR merges"
463+
description="Apply changes to your production database when you merge into your configured production GitHub branch"
464464
>
465465
<FormControl>
466466
<Switch

apps/studio/components/interfaces/Settings/Integrations/GithubIntegration/GithubSection.tsx

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -54,9 +54,9 @@ export const GitHubSection = () => {
5454
How does the GitHub integration work?
5555
</h3>
5656
<p className="text-sm text-foreground-light">
57-
Connecting to GitHub allows you to sync preview branches with a chosen GitHub
58-
branch, keep your production branch in sync, and automatically create preview
59-
branches for every pull request.
57+
Connect to GitHub to apply changes to your database when you merge into your
58+
production branch. If branching is enabled, each pull request gets its own preview
59+
database.
6060
</p>
6161
</div>
6262
<div>

0 commit comments

Comments
 (0)