chore(error-tracking): remove error-tracking-insights feature flag guard#59376
Merged
ablaszkiewicz merged 2 commits intoMay 21, 2026
Merged
Conversation
The insights tab is fully released, so the flag check is no longer needed. Generated-By: PostHog Code Task-Id: 64aacacc-50fe-4d9d-b366-5f7f8ec109ca
Contributor
|
🎭 Playwright didn't run on this PR — your changes touch code that could affect E2E behavior, but Playwright is opt-in via label now to keep CI cost down. Add the Most PRs don't need this. Real regressions still get caught on master and fix-forward. |
Contributor
|
Size Change: -6.77 kB (-0.01%) Total Size: 116 MB 📦 View Changed
ℹ️ View Unchanged
|
The flag constant had no remaining references in the frontend and spike alerting is fully released. Generated-By: PostHog Code Task-Id: 64aacacc-50fe-4d9d-b366-5f7f8ec109ca
Contributor
|
Reviews (1): Last reviewed commit: "chore(error-tracking): remove unused err..." | Re-trigger Greptile |
Contributor
There was a problem hiding this comment.
Pull request overview
Removes the now-redundant error-tracking-insights feature-flag gate so the Error Tracking “Insights” tab is always available, and cleans up the unused feature flag constant.
Changes:
- Always render the “Insights” tab in the Error Tracking scene (removes
useFeatureFlag('ERROR_TRACKING_INSIGHTS')guard). - Remove
ERROR_TRACKING_INSIGHTSfrom theFEATURE_FLAGSconstants map.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated no comments.
| File | Description |
|---|---|
| products/error_tracking/frontend/scenes/ErrorTrackingScene/ErrorTrackingScene.tsx | Removes the feature-flag conditional and always includes the Insights tab in the scene’s tabs list. |
| frontend/src/lib/constants.tsx | Deletes the ERROR_TRACKING_INSIGHTS entry from FEATURE_FLAGS now that it’s no longer referenced. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
cat-ph
approved these changes
May 21, 2026
Contributor
Author
Merge activity
|
ablaszkiewicz
deleted the
posthog-code/remove-error-tracking-insights-flag
branch
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
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
error-tracking-insightsfeature flag is fully released, so the conditional guard around the Insights tab in the error tracking scene is dead weight.Changes
useFeatureFlag('ERROR_TRACKING_INSIGHTS')check inErrorTrackingScene.tsxand always render the Insights tab.ERROR_TRACKING_INSIGHTSconstant fromfrontend/src/lib/constants.tsx.How did you test this code?
I'm an agent — I did not run the app manually. No automated tests were added or run for this purely conditional-removal change.
Publish to changelog?
no
Docs update
No docs change needed.
🤖 Agent context
Authored by PostHog Code on behalf of @ablaszkiewicz, who requested removing the feature flag guard now that the insights tab is fully rolled out. I located the flag's only conditional use in
ErrorTrackingScene.tsx, inlined the tab definition unconditionally, and removed the constant fromfrontend/src/lib/constants.tsxafter verifying no other references remained via grep. The othererror-tracking-insights-*string occurrences inChartCard.tsxare unrelated logic keys, not the flag.Created with PostHog Code