Skip to content

fix: move global_fetch_strictly_public to the correct folder #22017

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.

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

Merged
merged 1 commit into from
Apr 28, 2025

Conversation

vicb
Copy link
Contributor

@vicb vicb commented Apr 28, 2025

Summary

This PR moves the description for global_fetch_strictly_public to the correct folder so that it appears at https://developers.cloudflare.com/workers/configuration/compatibility-flags/ (it did not appear anywhere before this PR)

The original PR by @irvinebroque was opened in Nov 2024 when the description for the flags lived in src/content/compatibility_dates.

After #18176, the description for the flags was moved to src/content/compatibility_flags, however #18075 was not updated to reflect the new location when it was merged 2 weeks ago.

More information in the workerd repo

Screenshots (optional)

See https://vicb-fetch-public.preview.developers.cloudflare.com/workers/configuration/compatibility-flags/#global-fetch-strictly-public

image

Documentation checklist

Copy link
Contributor

hyperlint-ai bot commented Apr 28, 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

Moved the global_fetch_strictly_public documentation to the correct folder to ensure proper organization and accessibility.

  • Renamed and relocated the global_fetch_strictly_public documentation file.
  • Ensured adherence to the documentation style guide.
  • Allocated redirects for the renamed file.

Renamed Files

  • src/content/compatibility-flags/global-fetch-strictly-public.md

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.

Copy link
Contributor

@kodster28 kodster28 merged commit fe52c30 into production Apr 28, 2025
14 checks passed
@kodster28 kodster28 deleted the vicb/fetch-public branch April 28, 2025 18:56
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants