Skip to content

chore: move torch-xpu-run to intel/gpu-ai-skills@4a64a3157c18 - #72

Merged
xaleryb merged 1 commit into
mainfrom
sync/torch-xpu-run-83a1c64e55a0
Oct 22, 2026
Merged

xaleryb merged 1 commit into
mainfrom
sync/torch-xpu-run-83a1c64e55a0

Conversation

@github-actions

Copy link
Copy Markdown
Contributor

torch-xpu-run has changed in intel/gpu-ai-skills on main and this repository's copy of it has not. Opened by tools/check_upstream.py; the bytes are upstream's at the new commit, written by tools/sync_external.py --write.

  • pin: 0b4fafd09c5eb4cc5daf532d915ef5984a919775 -> 4a64a3157c1895ef4b48b861c81c445e4e161bcf
  • upstream diff: intel/gpu-ai-skills@0b4fafd...4a64a31
  • also changed upstream, each in its own pull request: model-can-it-fit, model-config-recommend

Merge or close this one on its own. Closing it declines this version of torch-xpu-run: it is not proposed again, and the next change upstream is.

What this does not decide is whether the new text should be merged. An import is somebody else's document, so a change in it is a change somebody made there: the checks below answer the structural half, and the diff is worth reading.

If the checks are waiting for approval, this pull request was opened with GITHUB_TOKEN: select Approve workflows to run in the merge box to start them.

@xaleryb
xaleryb merged commit 5fdf63e into main Oct 22, 2026
16 checks passed
@xaleryb
xaleryb deleted the sync/torch-xpu-run-83a1c64e55a0 branch October 22, 2026 03:01
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant