Skip to content

Fix Running on Device link in CUDA backend overview - #23397

Open
pratikgx wants to merge 1 commit into
pytorch:mainfrom
pratikgx:docs/fix-cuda-overview-link
Open

pratikgx wants to merge 1 commit into
pytorch:mainfrom
pratikgx:docs/fix-cuda-overview-link

Conversation

@pratikgx

@pratikgx pratikgx commented Oct 3, 2026 •

Copy link
Copy Markdown

Summary

The "Running on Device" link in the CUDA backend overview points to getting-started.md#running-on-device, which resolves to docs/source/backends/cuda/getting-started.md. That file doesn't exist, so the link is broken. The getting started guide is at docs/source/getting-started.md, so the link is now ../../getting-started.md#running-on-device. This matches the same link in backends/coreml/coreml-overview.md.

Test plan

Docs only. docs/source/getting-started.md exists on main and has a ## Running on Device heading, so the anchor resolves. No docs build was run.

cc @nil-is-all

@pratikgx
pratikgx requested a review from mergennachin as a code owner October 3, 2026 04:50
@pytorch-bot

pytorch-bot Bot commented Oct 3, 2026 •

Copy link
Copy Markdown

🔗 Helpful Links

🧪 See artifacts and rendered test results at hud.pytorch.org/pr/pytorch/executorch/23397

Note: Links to docs will display an error until the docs builds have been completed.

❌ 14 Awaiting Approval, 1 New Failure

As of commit fe33130 with merge base 0b3d26d (image):

AWAITING APPROVAL - The following workflows need approval before CI can run:

NEW FAILURE - The following job has failed:

  • Cadence Build & Test / Resolve CI docker image / resolve (gh)
    ##[error]Refusing to check out fork pull request code from a 'pull_request_target' workflow. This workflow runs with the base repository's GITHUB_TOKEN, secrets, default-branch cache scope, and runner access. Fetching and executing a fork's code in that trusted context commonly leads to "pwn request" vulnerabilities. To opt in, review the risks at https://gh.io/securely-using-pull_request_target and set 'allow-unsafe-pr-checkout: true' on the actions/checkout step.

This comment was automatically generated by Dr. CI and updates every 15 minutes.

@meta-cla meta-cla Bot added the CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. label Oct 3, 2026
@linux-foundation-easycla

linux-foundation-easycla Bot commented Oct 3, 2026 •

Copy link
Copy Markdown

CLA Signed
The committers listed above are authorized under a signed CLA.

  • ✅ login: pratikgx / name: Pratik Gandhi (fe33130)

@pratikgx

pratikgx commented Oct 3, 2026

Copy link
Copy Markdown
Author

@pytorchbot label "release notes: none"

@pytorch-bot pytorch-bot Bot added the release notes: none Do not include this in the release notes label Oct 3, 2026
@executorch-triage executorch-triage Bot added the community: contribution PRs coming from community (excluding hardware partners) label Oct 3, 2026

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

CLA Signed This label is managed by the Facebook bot. Authors need to sign the CLA before a PR can be reviewed. community: contribution PRs coming from community (excluding hardware partners) release notes: none Do not include this in the release notes

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant