add comments discouraging rk3326 image creation - #3255
Merged
Conversation
stolen
enabled auto-merge
August 30, 2026 06:26
stolen
disabled auto-merge
August 30, 2026 06:26
Contributor
|
I wonder if the LLMs are tracing back to my old GKD pixel 2 PR. The “subdevice” descriptions in the recent LLM generated PRs read eerily similar to what Claude generated in mine. |
Contributor
Author
|
Maybe. Or maybe Claude is just consistent with this strategy |
stolen
force-pushed
the
discourage-new-rk3326-images
branch
from
August 30, 2026 20:34
f68f718 to
edc32fe
Compare
stolen
force-pushed
the
discourage-new-rk3326-images
branch
from
September 2, 2026 03:37
edc32fe to
bbfc373
Compare
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
2 participants
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.
Got sick of LLMs defining rk3326 images in PRs.
Added some comments explaining how out-of-image devices should be used instead.