chore(web): Add isBranchFilteringEnabled flag to search_finished event

[brendan-kellam]

Summary by CodeRabbit

• Chores
  • Enhanced analytics tracking to capture branch filtering status in search events, providing improved insights into user search behavior.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[coderabbitai]

Caution

Review failed

The pull request is closed.

Walkthrough

The changes introduce tracking for branch filtering in search operations by adding an isBranchFilteringEnabled flag that detects when users filter across multiple branches (non-HEAD), propagates this data through the component hierarchy, and includes it in PostHog event analytics.

Changes

Cohort / File(s)	Summary
Branch filtering flag implementation packages/web/src/app/[domain]/search/components/searchResultsPage.tsx	Introduces isBranchFilteringEnabled computed flag using useMemo that detects if any file's branch differs from HEAD. Flag is propagated to SearchResultsPanel via props and included in search_finished event payload. Consolidates logic at page level by removing previous in-component memoization. Updates PanelGroupProps to accept and forward the flag.
PostHog event schema packages/web/src/lib/posthogEvents.ts	Adds isBranchFilteringEnabled: boolean property to search_finished event payload in PosthogEventMap.
Documentation CHANGELOG.md	Documents addition of isBranchFilteringEnabled flag to search_finished event tracking.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

✨ Finishing touches

• 📝 Generate docstrings

---

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

_{Comment @coderabbitai help to get the list of available commands and usage tips.}