Skip to content

Conversation

@daisyfaithauma
Copy link
Contributor

Summary

Screenshots (optional)

Documentation checklist

  • The documentation style guide has been adhered to.
  • If a larger change - such as adding a new page- an issue has been opened in relation to any incorrect or out of date information that this PR fixes.
  • Files which have changed name or location have been allocated redirects.

@hyperlint-ai
Copy link
Contributor

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

Updated documentation to include new examples and a detailed guide for extracting blog post content using the markdown endpoint.

  • Added examples for using the Workers Binding API and REST API in the get-started documentation.
  • Introduced a new guide for extracting blog post content as markdown using the markdown endpoint.
  • Provided detailed instructions for configuring environment variables and making API requests.

Modified Files

  • src/content/docs/browser-rendering/get-started.mdx

Added Files

  • src/content/docs/browser-rendering/how-to/markdown-extraction.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.

@daisyfaithauma daisyfaithauma marked this pull request as ready for review May 7, 2025 14:33
@daisyfaithauma daisyfaithauma requested review from a team, kathayl and mchenco as code owners May 7, 2025 14:33
@github-actions
Copy link
Contributor

github-actions bot commented May 7, 2025

@daisyfaithauma daisyfaithauma changed the title Release Notes - Automatic Request Headers [BRAPI]Release Notes - Automatic Request Headers May 8, 2025
@kathayl
Copy link
Contributor

kathayl commented May 8, 2025

looks like changelogs got mixed up. this is for browser rendering but in the ai gateway changelog

@kathayl kathayl enabled auto-merge (squash) May 9, 2025 15:42
- publish_date: "2025-04-30"
title: Automatic Request headers
description: |-
* [Clarified Automatic Request headers](/browser-rendering/reference/automatic-request-headers/) in Browser Rendering. These headers are unique to Browser Rendering and are automatically included and cannot be removed or overridden.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Would it be better to word this as "Clarified Automatic Request Headers are available in Browser Rendering"

Suggested change
* [Clarified Automatic Request headers](/browser-rendering/reference/automatic-request-headers/) in Browser Rendering. These headers are unique to Browser Rendering and are automatically included and cannot be removed or overridden.
* [Clarified Automatic Request headers](/browser-rendering/reference/automatic-request-headers/) in Browser Rendering. These headers are unique to Browser Rendering, and are automatically included and cannot be removed or overridden.

productAreaLink: /workers/platform/changelog/platform/
entries:
- publish_date: "2025-04-30"
title: Automatic Request headers
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For consistency with the description.

Suggested change
title: Automatic Request headers
title: Automatic Request Headers

@kathayl kathayl merged commit d464317 into production May 9, 2025
10 checks passed
@kathayl kathayl deleted the changelog branch May 9, 2025 16:23
daisyfaithauma added a commit that referenced this pull request May 13, 2025
* initial rest API guide

* added automatic request headers

* Revert commit

* moved to BRAPI
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.

6 participants