Repository navigation
CTX7-3075: Fix all broken anchors - #897
Conversation
|
Preview deployment for your docs. Learn more about Mintlify Previews.
💡 Tip: Enable Automations to automatically generate PRs for you. |
|
Docs7 for upstash.com
Commit |
![context7[bot]](https://avatars.githubusercontent.com/in/2083650?s=60&v=4){kind=small}
| <Tip> | ||
| You should also | ||
| set [`disableTelemetry` when triggering workflow runs via `client.trigger()`](/workflow/basics/client/trigger#param-disable-telemetry) to fully disable telemetry | ||
| set [`disableTelemetry` when triggering workflow runs via `client.trigger()`](/workflow/basics/client/trigger#body-disabletelemetry) to fully disable telemetry |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
enesgules
changed the title
Field links use Mintlify's param-<kebab name> form, which docs7 serves after upstash/docs7#497.
|
|
||
| For a more indepth tutorial on how to deploy to Vercel, check out this | ||
| [quickstart](/qstash/quickstarts/vercel-nextjs#4-deploy-to-vercel). | ||
| [quickstart](/qstash/quickstarts/vercel-nextjs#deploying-to-vercel). |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
| - **TypeScript SDK (`workflow-js`):** | ||
| - Added `retryDelay` option to dynamically program the retry duration. It can be configured on | ||
| [trigger](/workflow/basics/client/trigger#body-retrydelay), [context.call](/workflow/steps/call) | ||
| [trigger](/workflow/basics/client/trigger#param-retry-delay), [context.call](/workflow/steps/call) |
This comment was marked as outdated.
This comment was marked as outdated.
Sorry, something went wrong.
…w-anchors # Conflicts: # llms-full.txt # redis/overall/changelog.mdx
Co-authored-by: context7[bot] <236830434+context7[bot]@users.noreply.github.com>
ramazanoacar
left a comment
ramazanoacar
left a comment
There was a problem hiding this comment.
Fixing every broken anchor in one pass is really useful, and the tables in the description made it quick to review. I checked the & anchors on the live site (subscribe-&-publish-commands, analytics-&-dashboard) and they're correct. This also corrects the -and- form that landed on main in db196a4.
One thing I'd like fixed before merge:
The Redis changelog lost an entry. The merge from main (1a39c78f) dropped the October 2026 Insights entry from redis/overall/changelog.mdx, and it's gone from llms-full.txt too. That entry was added on main in 6998a1a6, so it looks like a conflict was resolved toward the older version. Could you restore it and regenerate llms-full.txt?
Small nits, not blocking:
redis/search/index-management.mdxandregex.mdx: the links still say "Text Field Options" but now point to#tokenization-&-stemming. Maybe rename the link text to "Tokenization & Stemming"?- The description says
llms-full.txtisn't changed here, but the regen commits do touch it. It might be worth updating that line.
Happy to approve once the changelog entry is back. As noted, this should merge after upstash/docs7#497 is deployed.
…ink texts The earlier merge from main kept the older changelog and dropped the Insights entry (6998a1a). The search links now name the section they open.
|
Thanks, good catch. The Oct 2026 Insights entry is restored (my conflict resolution kept the old file), and |
ramazanoacar
left a comment
ramazanoacar
left a comment
There was a problem hiding this comment.
LGTM. I checked every target: the six field links (param-verbose, param-url, param-base-url, param-qstash-client, param-failure-function, param-disable-telemetry on serve/advanced; param-retry-delay and param-disable-telemetry on client/trigger) each name a field that appears exactly once on its page, so none will resolve to a -1 variant. All nine heading anchors exist on the live upstash.com pages, including the & ones (subscribe-&-publish-commands, pipelines-&-transactions, analytics-&-dashboard, tokenization-&-stemming), which the renderer keeps as a literal ampersand. Dropping the misspelled serveMany anchor and the dead chat-API sentence is right.
Two small notes on the description, nothing to change in the diff: the quickstart security#… row is already in the new form on the branch (the fix landed via main), and the link-rot failure is the same 52 links every PR reports, so it is not about these anchors.
Hold the merge until docs7#497 is deployed; until then the #param-… field links are dead on the live site.
This branch was successfully deployed
2 participants
Summary
This PR fixes every link in the repo that points to an anchor its target page does not have: 24 links in 22 files.
Merge after upstash/docs7#497 is deployed. Field links here use Mintlify's form,
#param-<kebab-name>. docs7 renders that form only after #497. Today docs7 renders#path-…/#body-….Field links (Workflow)
basics/client/trigger.mdxserve/advanced#param-disable-telemetrybasics/serve/advanced.mdxclient/trigger#param-disable-telemetrytroubleshooting/vercel.mdxserve/advanced#param-qstash-clientchangelog.mdxclient/trigger#body-retrydelay(docs7 form, #894)#param-retry-delaytroubleshooting/general.mdx#path-verbose,#path-baseurl,#path-url(docs7 form, #894)#param-verbose,#param-base-url,#param-url_snippets/workflow/logs.mdx/workflow/basics/serve#failurefunction/workflow/basics/serve/advanced#param-failure-functionHeading links
workflow/quickstarts/nextjs-fastapi.mdx,nextjs-flask.mdxsecurity#using-qstashs-built-in-request-verification-recommended#built-in-request-verification-recommendedworkflow/agents/patterns/orchestrator-workers.mdxagents/overview#multi-agentsagents/features#multi-agentsqstash/overall/changelog.mdxretry#retry-after-header#retry-after-headersqstash/recipes/periodic-data-updates.mdxvercel-nextjs#4-deploy-to-vercel#deploying-to-vercelredis/overall/changelog.mdxrestapi#subscribe-command#subscribe-&-publish-commandsredis/sdks/py/commands/overview.mdxfeatures#pipelines-and-transactions#pipelines-&-transactionsredis/sdks/ratelimit-ts/gettingstarted.mdx,overview.mdxfeatures#analytics-and-dashboard#analytics-&-dashboardredis/sdks/ratelimit-ts/costs.mdxfeatures#auto-ip-deny-listtraffic-protection#auto-ip-deny-listredis/search/index-management.mdx,query-operators/field-operators/regex.mdxschema-definition#text-field-options#tokenization-&-stemming(link text now "Tokenization & Stemming")I checked each new heading anchor on the live upstash.com page.
Removed anchors
workflow/steps/call.mdx:serveMany#using-serve-manynyis a typo, and the page has no headings. The link now goes to the page.qstash/integrations/llm.mdx: I removed "Use the chat API for streaming completions."#chat-apipoints to a section that was deleted in 2024 (cf1df008), and no other page documents a QStash chat API.llms.txtandllms-full.txtchange only through the llms workflow's regeneration commits on this branch.Part of CTX7-3075