[Zaimwa9]

Thanks for submitting a PR! Please check the boxes below:

• I have read the Contributing Guide.
• I have added information to docs/ if required so people know about the feature.
• I have filled in the "Changes" section below.
• I have filled in the "How did you test this code" section below.

Changes

On self-hosted, "Send your first event" for ClickHouse, Databricks and bring-your-own PostgreSQL posts to Flagsmith Cloud's ingestion server, which rejects the self-hosted key, so the event never lands and the button never goes away.

• Show the button for customer warehouses only on SaaS; the Flagsmith database connection keeps it on self-hosted, since it posts to the installation's own API.

How did you test this code?

Unit tests for the extracted shouldShowSendFirstEvent predicate.

[vercel]

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

Project	Deployment	Actions	Updated
flagsmith-frontend-preview	Ready	Preview	Nov 4, 2026 4:23pm UTC
flagsmith-frontend-staging	Ready	Preview	Nov 4, 2026 4:23pm UTC

1 Skipped Deployment

Project	Deployment	Actions	Updated
docs	Ignored		Nov 4, 2026 4:23pm UTC

[coderabbitai]

Walkthrough

The change adds and tests shouldShowSendFirstEvent to determine whether to show the first-event prompt. WarehouseConnectionCard now calls this helper with the connection and SaaS status.

Estimated code review effort: 2 (Simple) | ~10 minutes

Merge Risk: Minimal · up to ec57f

The change restricts customer-warehouse prompts on self-hosted installations while retaining the Flagsmith database prompt. The remaining suggestions improve test coverage and do not block merging after normal checks.

- [ ] Autofix · Keep fixing CodeRabbit findings and required CI, and resolving merge conflicts

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

• X
• Mastodon
• Reddit
• LinkedIn

[github-actions]

Docker builds report

Image	Build Status	Security report
ghcr.io/flagsmith/flagsmith-api-test:pr-8874	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-e2e:pr-8874	Finished ✅	Skipped
ghcr.io/flagsmith/flagsmith-api:pr-8874	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith:pr-8874	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-private-cloud:pr-8874	Finished ✅	Results ✅
ghcr.io/flagsmith/flagsmith-frontend:pr-8874	Finished ✅	Results ✅

[coderabbitai]

Nitpick comments: 2

frontend/web/components/pages/environment-settings/tabs/warehouse-tab/__tests__/warehouseTypes.test.ts: 2

124-135: Trivial · Maintainability & Code Quality · Quick win

Add a managed Flagsmith case for the connected status.

The flagsmith branch of shouldShowSendFirstEvent hides the button for connected connections. The new cases cover only created and pending_connection. Removing the connected check would leave the suite passing. Add a row with status: 'connected' and the expected result false.

Suggested fix

     [
       { config: {}, warehouse_type: 'flagsmith' },
       { status: 'pending_connection', total_events_received: null },
       true,
       false,
     ],
+    [
+      { config: {}, warehouse_type: 'flagsmith' },
+      { status: 'connected', total_events_received: null },
+      true,
+      false,
+    ],

---

115-117: Trivial · Functional Correctness · Quick win

Add Databricks and PostgreSQL customer-warehouse cases for SaaS.

The customer-warehouse cases use only ClickHouse. If CUSTOMER_WAREHOUSE_TYPES dropped databricks or postgres, every test in this block would still pass. The Flagsmith database case returns before the list check, so no case tests an ordinary PostgreSQL connection against the list.

Suggested test cases

     [byo, { status: 'connected', total_events_received: 3 }, true, false],
+    [
+      { config: {}, warehouse_type: 'databricks' },
+      { status: 'connected', total_events_received: 0 },
+      true,
+      true,
+    ],
+    [
+      { config: {}, warehouse_type: 'postgres' },
+      { status: 'connected', total_events_received: 0 },
+      true,
+      true,
+    ],

Review info

Run configuration

• Source mode: Auto
• Repository: Unavailable
• Branch: Unavailable
• File: No configuration file from this repository applied
• Commit: Unavailable
• Layers: Organization UI
• Review profile: ASSERTIVE
• Plan: Advanced
• Run ID: 1e3a8e67-88a7-4a2d-ba99-701cb44456ad

Commits

Reviewing files that changed from the base of the PR and between af5c88f and ec57f57.

Files selected for processing: 3

• frontend/web/components/pages/environment-settings/tabs/warehouse-tab/WarehouseConnectionCard.tsx
• frontend/web/components/pages/environment-settings/tabs/warehouse-tab/__tests__/warehouseTypes.test.ts
• frontend/web/components/pages/environment-settings/tabs/warehouse-tab/warehouseTypes.ts

Included review availability: This review used your included allowance. Your plan provides up to 8 included reviews per hour; 7 remain after this review.

[github-actions]

✅ private-cloud · depot-ubuntu-latest-arm-16 — run #22879 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-arm-16)

 2 passed

Details

 2 tests across 2 suites
 12 seconds
 ec57f57
 🔄 Run: #22879 (attempt 1)

🗂️ Previous results

✅ private-cloud · depot-ubuntu-latest-16 — run #22879 (attempt 1)

Playwright Test Results (private-cloud - depot-ubuntu-latest-16)

 4 passed

Details

 4 tests across 4 suites
 3.6 seconds
 ec57f57
 🔄 Run: #22879 (attempt 1)

✅ oss · depot-ubuntu-latest-arm-16 — run #22879 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-arm-16)

 1 passed

Details

 1 test across 1 suite
 35.7 seconds
 ec57f57
 🔄 Run: #22879 (attempt 1)

✅ oss · depot-ubuntu-latest-16 — run #22879 (attempt 1)

Playwright Test Results (oss - depot-ubuntu-latest-16)

 1 passed

Details

 1 test across 1 suite
 31.7 seconds
 ec57f57
 🔄 Run: #22879 (attempt 1)

[github-actions]

Visual Regression

24 screenshots compared. See report for details.
View full report