GitHub user zyratlo added a comment to the discussion: AI-generated descriptions in issues and PRs
Here's my opinion. Issues are meant to be more abstract, describing a problem or suggesting a fix, so I don't think exact implementation details belong there. Human readability matters more, and diagrams or pictures can add a lot. Some technical detail is fine for developers who can read and follow it, but there's such a thing as being so verbose that only agents can get through it. PRs are more technical by nature since the code changes are right there. But if the description is too verbose, reading it is basically the same as reading the source, which defeats the point of having a description at all. I agree the right balance is a section at the top written for humans, and optionally a longer technical explanation below that's mainly for agents. If the real problem is agents writing descriptions that are too verbose and hard to read, we can require the poster to review the agent's output before publishing. The goal would be to improve human readability and cut down on wordiness, instead of assuming the generated content is good enough to post as-is. GitHub link: https://github.com/apache/texera/discussions/7377#discussioncomment-17937883 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
