UPSTREAM PR #18388: (proposal) contributing: tighten AI usage policy#711
Open
UPSTREAM PR #18388: (proposal) contributing: tighten AI usage policy#711
Conversation
loci-dev
had a problem deploying
to
PROD__AL_DEMO
GitHub Actions
Failure
|
Explore the complete analysis inside the Version Insights Perfect! I've generated the summary report for your project. Here's what the analysis shows: Performance Summary ReportProject Details:
Version Comparison:
SummaryThe performance analysis shows no significant performance regressions or improvements between the two versions. Key Findings:
Conclusion: Pull Request #711 has a neutral performance impact and appears safe to merge from a performance perspective, as it maintains performance stability without introducing measurable regressions. |
loci-dev
force-pushed
the
main
branch
27 times, most recently
from
559165d to
ae8ce6f
Compare
loci-dev
force-pushed
the
main
branch
30 times, most recently
from
7b2e535 to
bfd3c27
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.
Mirrored from ggml-org/llama.cpp#18388
In my personal case, nitpicking AI-generated PRs took me quite a lot of time, which lead to net-0 or even negative productivity (even with the help of AI-assisted reviewing)
So I make this proposition to see if other maintainers agree. This is inspired by p5.js's policy.
Contributor often circumvent by saying that their code has gone though significant manual changes. But in practice, they don't change the structure of the code that much. Some even hide the fact that they don't understand the code by forwarding my questions/my reviews directly to AI. That's why I'm proposing now limit the usage of AI to be assisting-only, not for generating the first version of the code, then manually fix it.
This PR is written by me, proofreading by AI.