Skip to content

[Page Shield] Clarify alert handling #21666

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom
Merged
merged 2 commits into from
Apr 14, 2025
Merged

[Page Shield] Clarify alert handling #21666

merged 2 commits into from
Apr 14, 2025

Conversation

@pedrosousa
Copy link
Contributor

@pedrosousa pedrosousa commented Apr 14, 2025

Summary

Small update. Reported via internal chat.

@pedrosousa pedrosousa requested a review from a team as a code owner April 14, 2025 10:31
@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented Apr 14, 2025

Howdy and thanks for contributing to our repo. The Cloudflare team reviews new, external PRs within two (2) weeks. If it's been two weeks or longer without any movement, please tag the PR Assignees in a comment.

We review internal PRs within 1 week. If it's something urgent or has been sitting without a comment, start a thread in the Developer Docs space internally.

PR Change Summary

Clarified alert handling procedures in the Page Shield documentation.

  • Updated the explanation regarding malicious domain classification.
  • Added a note on contacting the account team for false positive classifications.

Modified Files

  • src/content/docs/page-shield/best-practices/handle-an-alert.mdx
How can I customize these reviews?

Check out the Hyperlint AI Reviewer docs for more information on how to customize the review.

If you just want to ignore it on this PR, you can add the hyperlint-ignore label to the PR. Future changes won't trigger a Hyperlint review.

Note specifically for link checks, we only check the first 30 links in a file and we cache the results for several hours (for instance, if you just added a page, you might experience this). Our recommendation is to add hyperlint-ignore to the PR to ignore the link check for this PR.

@github-actions github-actions bot added size/xs product:page-shield Issues or PRs related to Page Shield labels Apr 14, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Apr 14, 2025 •
edited
Loading

Preview URL: https://26cfeb76.preview.developers.cloudflare.com
Preview Branch URL: https://pedro-2025-04-14-page-shield-clarify-alert-handling.preview.developers.cloudflare.com

Files with changes (up to 15)

Original Link Updated Link
https://developers.cloudflare.com/page-shield/best-practices/handle-an-alert/ https://pedro-2025-04-14-page-shield-clarify-alert-handling.preview.developers.cloudflare.com/page-shield/best-practices/handle-an-alert/

Oxyjun
Oxyjun reviewed Apr 14, 2025
View reviewed changes
@pedrosousa pedrosousa merged commit 04d101f into production Apr 14, 2025
11 checks passed
@pedrosousa pedrosousa deleted the pedro/2025-04-14-page-shield-clarify-alert-handling branch April 14, 2025 13:25
RebeccaTamachiro pushed a commit that referenced this pull request Apr 21, 2025
@pedrosousa @Oxyjun @RebeccaTamachiro
[Page Shield] Clarify alert handling (#21666)
2d99aca 
---------

Co-authored-by: Jun Lee <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

@Oxyjun Oxyjun Oxyjun approved these changes

Assignees

No one assigned

Labels

product:page-shield Issues or PRs related to Page Shield size/xs

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

2 participants

@pedrosousa @Oxyjun