refactor(tasks): create subdirectory for alerts code

[dhable]

The alerts code and some of our private source tasks are becoming complex enough for multiple files. In order to keep the code clearer to debug and read, this commit moves the check alerts tasks into a sub-directory for just alert related code.

[changeset-bot]

⚠️ No Changeset found

Latest commit: 3001978

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

[vercel]

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

Project	Deployment	Preview	Comments	Updated (UTC)
hyperdx-v2-oss-app	Ready	Preview	Comment	Oct 23, 2025 8:16am

[claude]

PR Review: Refactor alerts code into subdirectory

✅ No critical issues found.

This is a clean refactoring that moves alert-related code into a dedicated subdirectory structure. The changes are well-executed:

What was done:

• Moved /tasks/checkAlerts.ts → /tasks/checkAlerts/index.ts
• Moved /tasks/providers/ → /tasks/checkAlerts/providers/
• Moved /tasks/template.ts → /tasks/checkAlerts/template.ts
• Updated all import paths correctly across the codebase
• Maintained test file organization

Verified:

• ✅ All import paths updated correctly
• ✅ No remaining references to old paths (@/tasks/providers, @/tasks/template)
• ✅ Relative imports properly adjusted (e.g., from .. in providers/default.ts)
• ✅ Test files moved and imports updated
• ✅ Main task entry point (tasks/index.ts) correctly imports from new location

Code quality:

• Follows project conventions for module organization
• Improves codebase maintainability by grouping related functionality
• No functional changes, pure refactoring

[github-actions]

E2E Test Results

✅ All tests passed • 26 passed • 3 skipped • 243s

Status	Count
✅ Passed	26
❌ Failed	0
⚠️ Flaky	0
⏭️ Skipped	3

View full report →