Skip to content

Feat(dashboard): show the Betterstack incident title in the dashboard#3006

Open
samejr wants to merge 3 commits intomainfrom
feat(webapp)-imrpoved-incident-notification
Open

Feat(dashboard): show the Betterstack incident title in the dashboard#3006
samejr wants to merge 3 commits intomainfrom
feat(webapp)-imrpoved-incident-notification

Conversation

@samejr
Copy link
Member

@samejr samejr commented Feb 5, 2026

When the incident panel is displayed, show the title added to BetterStack as the contents of the incident panel.

I've also brightened the UI so it's more visible.

CleanShot 2026-02-04 at 20 46 36@2x
Open with Devin

@changeset-bot
Copy link

changeset-bot bot commented Feb 5, 2026

⚠️ No Changeset found

Latest commit: bcb2654

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

@coderabbitai
Copy link
Contributor

coderabbitai bot commented Feb 5, 2026

Walkthrough

This pull request refactors incident status handling across the application. A new useIncidentStatus hook and IncidentLoaderData type are exported from the incidents route, enabling polling of incident status for managed-cloud deployments. The backend replaces the getIncidents() method with getIncidentStatus(), which returns structured incident data including status and title. Styling for the incident panel is updated from warning to yellow theme. A shouldRevalidate constant is added to prevent route revalidation when other fetchers submit. The Help & Feedback popover gains a focus styling utility class.

Estimated code review effort

🎯 3 (Moderate) | ⏱️ ~25 minutes

Rationale: The changes span three files with varied complexity. The first file is trivial (single CSS class addition). The second file involves moderate refactoring with new public exports (hook and type) alongside styling updates and component restructuring (+62/-59 lines). The third file requires careful review due to significant API changes, new types, caching mechanism replacement, and paging logic (+132/-46 lines). While individually heterogeneous within each file, the overall scope remains contained to incident status management with clear separation of concerns.

🚥 Pre-merge checks | ✅ 1 | ❌ 2
❌ Failed checks (2 warnings)
Check name Status Explanation Resolution
Docstring Coverage ⚠️ Warning Docstring coverage is 20.00% which is insufficient. The required threshold is 80.00%. Write docstrings for the functions missing them to satisfy the coverage threshold.
Description check ⚠️ Warning The pull request description is minimal and lacks key required sections from the template including issue reference, complete testing details, and proper changelog information. Add 'Closes #' reference, provide detailed testing steps in the Testing section, expand the Changelog with comprehensive change descriptions, and ensure all template sections are properly completed.
✅ Passed checks (1 passed)
Check name Status Explanation
Title check ✅ Passed The title accurately describes the main change: displaying the BetterStack incident title in the dashboard incident panel, which is the primary objective of this PR.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
  • 📝 Generate docstrings
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch feat(webapp)-imrpoved-incident-notification

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

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

@samejr samejr marked this pull request as ready for review February 5, 2026 05:25
Copy link

@devin-ai-integration devin-ai-integration bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

✅ Devin Review: No Issues Found

Devin Review analyzed this PR and found no potential bugs to report.

View in Devin Review to see 4 additional findings.

Open in Devin Review

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants