Skip to content

fix: clarify no-alert selection - #1704

Merged
crypt0rr merged 3 commits into
mainfrom
t3/rename-no-alerts-choice
Oct 25, 2026
Merged

crypt0rr merged 3 commits into
mainfrom
t3/rename-no-alerts-choice

Conversation

@crypt0rr

@crypt0rr crypt0rr commented Oct 25, 2026 •

Copy link
Copy Markdown
Owner

Closes #1701

Summary

Rename the no-alert choice to “Use no alerts” so it describes selecting an empty alert destination list. Keep the selection on the notification step, preserve its status announcement and draft state, and retain the explicit Review monitor action and role-specific guidance. Add regression coverage for administrator and operator flows, keyboard selection/review, and narrow layout. Update the first-scan guide.

Validation

Hosted checks can provide the final gate.

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Oct 25, 2026 •

Copy link
Copy Markdown

Deploying edgewatch with  Cloudflare Pages  Cloudflare Pages

Latest commit: c94a7d2
Status: ✅  Deploy successful!
Preview URL: https://47a75503.edgewatch-cpd.pages.dev
Branch Preview URL: https://t3-rename-no-alerts-choice.edgewatch-cpd.pages.dev

View logs

@crypt0rr crypt0rr changed the title Clarify no-alert selection label fix: clarify no-alert selection Oct 25, 2026
@crypt0rr
crypt0rr force-pushed the t3/rename-no-alerts-choice branch 2 times, most recently from 25f4fff to e704cf4 Compare October 25, 2026 16:27
@crypt0rr
crypt0rr force-pushed the t3/rename-no-alerts-choice branch from e704cf4 to c94a7d2 Compare October 25, 2026 16:44
@crypt0rr
crypt0rr merged commit 394324b into main Oct 25, 2026
17 of 18 checks passed
@crypt0rr
crypt0rr deleted the t3/rename-no-alerts-choice branch October 25, 2026 16:58
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.

[P3] Rename the no-alerts choice to match what it does

1 participant