Conversation
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
thiagosalvatore
added
the
skip-agent-review
Contributor
|
Reviews (1): Last reviewed commit: "fix(warehouse): correct supabase connect..." | Re-trigger Greptile |
2 tasks
Gilbert09
approved these changes
Jul 1, 2026
inkeep Bot
added a commit
to PostHog/posthog.com
that referenced
this pull request
Jul 1, 2026
Reflects PostHog/posthog#67276 — the old path (Project Settings → Database → Connection pooling) is no longer reliable in Supabase's current dashboard. Updated both the setup step and the IPv4 note to direct users to click Connect → Direct tab → Session pooler / Direct connection.
thiagosalvatore
pushed a commit
to PostHog/posthog.com
that referenced
this pull request
Jul 1, 2026
Reflects PostHog/posthog#67276 — the old path (Project Settings → Database → Connection pooling) is no longer reliable in Supabase's current dashboard. Updated both the setup step and the IPv4 note to direct users to click Connect → Direct tab → Session pooler / Direct connection. Co-authored-by: inkeep[bot] <257615677+inkeep[bot]@users.noreply.github.com>
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Problem
The help caption on the host field when adding Supabase as a Data warehouse source pointed users to Project settings → Database → Connection pooling to find their connection details. That is not a reliable path in Supabase's current dashboard, so users struggled to locate the right host and username.
Changes
Rewrote the host-field caption to describe the correct flow: click Connect in the top bar, open the Direct tab, and pick Session pooler or Direct connection (the URL shows at the bottom). The CDC guidance,
postgres.<project-ref>username hint, and IPv6-only / IPv4-add-on facts are unchanged. This is a single string constant (_SUPABASE_POOLER_HOST_CAPTION) rendered as markdown on the source form.How did you test this code?
No automated tests were added or run for a copy-only change. I (Claude) confirmed the constant is still wired to the host field's
captionand that the surrounding logic is untouched. The caption renders as markdown in the existing source form, so no codegen or migration is involved.Automatic notifications
🤖 Agent context
Autonomy: Human-driven (agent-assisted)
Thiago directed this change; I (Claude) made the edit. We first scoped where the text lived and found three related spots (the host caption, a validation error hint, a frontend CDC banner, and a dev skill doc), then deliberately limited the fix to just the host caption since that was the only one carrying the stale navigation path. No repo skills were invoked.