doc: ban AI-generated PR descriptions [no ci]#18765
Merged
JohannesGaessler merged 1 commit intoggml-org:masterfrom Jan 13, 2026
Merged
doc: ban AI-generated PR descriptions [no ci]#18765JohannesGaessler merged 1 commit intoggml-org:masterfrom
JohannesGaessler merged 1 commit intoggml-org:masterfrom
Conversation
ngxson
approved these changes
Jan 11, 2026
Contributor
There was a problem hiding this comment.
Just keep in mind that things written here is only for reference, in case people ask us about the policy. Unfortunately I think some people will still lazy and ask AI to write the description.
On the bright side, obvious mistakes like this can be a good way to reject a PR. Models like Claude be quite both manipulative and stupid at the same time.
Member
|
Yes please, if someone wants to submit a PR I expect them to write the PR description by themselves. That at least tells us whether they understand anything from the PR (in case it's AI-generated). The worst thing out there is AI-generated descriptions for AI-generated PRs and people who don't really understand either. |
taronaeo
approved these changes
Jan 12, 2026
gary149
pushed a commit
to gary149/llama-agent
that referenced
this pull request
Jan 13, 2026
dillon-blake
pushed a commit
to Boxed-Logic/llama.cpp
that referenced
this pull request
Jan 15, 2026
MaheshJakkala
pushed a commit
to MaheshJakkala/llama.cpp
that referenced
this pull request
Mar 15, 2026
Seunghhon
pushed a commit
to Seunghhon/llama.cpp
that referenced
this pull request
Apr 26, 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.
We could maybe explicitly ban the use of language models to generate PR descriptions. In principle I think that this is maybe one of the more legitimate use cases for language models (if you wrote the code yourself and fully understand it). But basically all of the time-wasting slop PRs that we want to reject use language models to generate PR descriptions; the people pushing the submit button simply have no other way of creating the appearance of understanding the code they submit. So potentially this change would save maintainers a bit of time.
I personally never use language models for summarizing pull requests, and I would consider the potential time savings vs. actually writing the code negligible anyways (because I already know what it does). But I don't know the workflows of other maintainers/contributors. But we can also just write down strict rules to be followed "officially" and then make exceptions on a case-by-case basis for people who have proven themselves.