chore: move performance-patterns to intel/intel-performance-skills@3e33aecabb95 - #41
Merged
Merged
Conversation
github-actions
Bot
requested review from
benjaminum,
napetrov and
xaleryb
as code owners
September 28, 2026 23:58
napetrov
approved these changes
Sep 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
performance-patternshas changed inintel/intel-performance-skillsonmainand this repository's copy of it has not. Opened bytools/check_upstream.py; the bytes are upstream's at the new commit, written bytools/sync_external.py --write.e9d0b6410fb1ad7a50fb81e0868fd23ae886882c->3e33aecabb956ec48526b3f842f4f70ae96d98ffMerge or close this one on its own. Closing it declines this version of
performance-patterns: 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.