Hyperlint Automation: Broken Link Fixes #20142
Conversation
hyperlint-ai
bot
requested review from
a team,
elithrar and
maheshwarip
as code owners
![hyperlint-ai[bot]](https://avatars.githubusercontent.com/in/718456?s=60&v=4){kind=small}
|
|
||
| - A [queue created](/queues/get-started/#3-create-a-queue) via the Cloudflare dashboard or the [wrangler CLI](/workers/wrangler/install-and-update/). | ||
| - A [configured **producer** binding](/queues/configuration/configure-queues/#producer) in the Cloudflare dashboard or Wrangler file. | ||
| - A [configured **producer** binding](/queues/configuration/configure-queues/#producer-worker-configuration-worker-configuration) in the Cloudflare dashboard or Wrangler file. |
There was a problem hiding this comment.
This page: https://developers.cloudflare.com/queues/examples/use-queues-with-durable-objects/
has a broken internal link to: https://developers.cloudflare.com/queues/configuration/configure-queues/.
The fragment producer does not exist.
By looking at the page: https://developers.cloudflare.com/queues/configuration/configure-queues/
The best fragment to use seems to be: #producer-worker-configuration
There was a problem hiding this comment.
@bllchmbrs FYI This Hyperlint suggestion to fix the broken link is not correct, for some reason... The previous one in this PR, fixing a link to the same destination, was correct.
Update: Oh, the comment text is correct! It mentions #producer-worker-configuration, but that's not what's in the PR changes.
Adding a screenshot because I'm fixing it in another commit (even though you can always check the individual first commit):
|
|
||
| - A [queue created](/queues/get-started/#3-create-a-queue) via the [Cloudflare dashboard](https://dash.cloudflare.com) or the [wrangler CLI](/workers/wrangler/install-and-update/). | ||
| - A [configured **producer** binding](/queues/configuration/configure-queues/#producer) in the Cloudflare dashboard or Wrangler file. | ||
| - A [configured **producer** binding](/queues/configuration/configure-queues/#producer-worker-configuration) in the Cloudflare dashboard or Wrangler file. |
There was a problem hiding this comment.
This page: https://developers.cloudflare.com/queues/examples/publish-to-a-queue-over-http/
has a broken internal link to: https://developers.cloudflare.com/queues/configuration/configure-queues/.
The fragment producer does not exist.
By looking at the page: https://developers.cloudflare.com/queues/configuration/configure-queues/
The best fragment to use seems to be: #producer-worker-configuration
github-actions
bot
added
product:queues
|
Howdy and thanks for contributing to our repo. We review new, external PRs within 2 weeks. If it's been longer than then without any movement, tag the PR Assignees in a comment. |
src/content/docs/queues/examples/use-queues-with-durable-objects.mdx
Outdated
Show resolved
Hide resolved
workers-devprod
added
the
contribution
|
Congratulations @Hyperlint-AI[bot], the maintainer of this repository has issued you a holobyte! Here it is: https://holopin.io/holobyte/cm7ell41622110ck118w1886p This badge can only be claimed by you, so make sure that your GitHub account is linked to your Holopin account. You can manage those preferences here: https://holopin.io/account. |
4 participants
Broken Link Fix Proposal(s)
The goal of this pull request is to fix broken links in the documentation.
Proposing changes to the following files:
to edit this branch locally, run:
🗣️Leave us feedback
This pull request is part of a series of Hyperlint Automations to ease the burden of maintaining documentation.
We'll be introducing this automation, and others, over the coming months. These automations will always open pull requests(or issues) prior to making changes.
If this is not the change you want, please close this pull request and let us know what you'd like to see.
This feature may introduce erroneous changes (although we work hard to make sure that doesn't happen). Please review the changes before merging.
❌ Limitations:
At this time, Hyperlint can't respond to pull requests or issues.
📩 Need Help?
Please reach out to support with any requests, questions, or concerns.