Skip to content

Conversation

@ToriLindsay
Copy link
Contributor

WIP!
Working with @mgalicer on creating Privacy Proxy section rather than adding it to Privacy Gateway. Pulling content from #18646.

@hyperlint-ai
Copy link
Contributor

hyperlint-ai bot commented Mar 10, 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

Created a new section for the Cloudflare Privacy Proxy, separating it from the Privacy Gateway and providing comprehensive documentation on its features and functionality.

  • Added an overview page for the Cloudflare Privacy Proxy.
  • Introduced a 'Get Started' guide for users.
  • Documented the Privacy API and token validation processes.
  • Outlined client initialization and token issuance procedures.

Added Files

  • src/content/docs/privacy-proxy/index.mdx
  • src/content/docs/privacy-proxy/privacy-proxy.mdx
  • src/content/docs/privacy-proxy/reference.mdx
  • src/content/docs/privacy-proxy/token-api.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.

What is Hyperlint?

Hyperlint is an AI agent that helps you write, edit, and maintain your documentation.

Learn more about the Hyperlint AI reviewer and the checks that we can run on your documentation.

@ToriLindsay
Copy link
Contributor Author

@mgalicer I didn't finish moving over the content because I was hitting errors, and I definitely still need to add some frontmatter, but I wanted to open it so you can start organizing the content as we discussed. Thanks!

@github-actions
Copy link
Contributor

Howdy and thanks for contributing to our repo. 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.

@kodster28 kodster28 closed this Jun 17, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

7 participants