Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

list of suggestions is too long #64

Closed
yegor256 opened this issue Mar 26, 2024 · 3 comments
Closed

list of suggestions is too long #64

yegor256 opened this issue Mar 26, 2024 · 3 comments

Comments

@yegor256
Copy link

Take a look at this one: yegor256/qulice#1242 (comment)

The list of suggestions is too long. Because of this, programmers simply ignore the entire message. Would be great to limit the list of suggestions to just three, to increase the probably of improvement.

Copy link

@yegor256 thanks for the report, but here some unclear moments:

  • The bug report is not formatted in a structured manner, making it difficult to understand the problem, steps to reproduce, and expected behavior.
  • There is no clear title for the bug report, making it hard for developers to understand the issue at a glance.
  • The description of the issue lacks necessary details such as the software version, operating system, and any error messages that might help in identifying and fixing the issue.
  • The bug report does not provide a clear step-by-step guide on how to reproduce the issue, which is crucial for developers to identify and fix the problem.
  • The bug report does not include any screenshots or attachments that could visually illustrate the issue, if applicable.
  • The bug report does not mention the priority level of the issue, which helps developers understand the urgency of the bug and allocate resources accordingly.
  • The bug report does not include any assignee or any indication of who is working on the issue or when it might be resolved.
  • The bug report does not contain any context about similar issues or whether this is a known issue. This information is helpful for developers to understand the scope and potential root causes of the problem.
  • The bug report does not include any information regarding potential workarounds or temporary fixes that users can employ while the issue is being addressed.
  • The list of suggestions is too long, limiting the effectiveness of the bug report. Consider limiting the list to just three suggestions to increase the likelihood of improvement.

Please fix the bug report in order it to get resolved faster.
Analyzed with Phind/Phind-CodeLlama-34B-v2

@h1alexbel
Copy link
Contributor

@yegor256 thanks for the report. Got it. I like the idea of limiting the number of "things to improve"

h1alexbel added a commit that referenced this issue Mar 26, 2024
h1alexbel added a commit that referenced this issue Mar 26, 2024
h1alexbel added a commit that referenced this issue Mar 26, 2024
h1alexbel added a commit that referenced this issue Mar 26, 2024
@h1alexbel h1alexbel mentioned this issue Mar 26, 2024
@h1alexbel
Copy link
Contributor

@yegor256 now it should generate maximum 3 suggestions per issue/puzzle

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants