-
Notifications
You must be signed in to change notification settings - Fork 1
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
reports are too verbose #98
Comments
@yegor256 thanks for the report, here is a feedback: Problems
Suggestions
Please fix the bug report in order it to get resolved faster. |
@yegor256 thanks for reporting this problem. Agreed, our improvements suggestion system is not good as we want, our next step is to make one suggestion only. |
@rultor release, tag is |
@h1alexbel OK, I will release it now. Please check the progress here |
@h1alexbel Done! FYI, the full log is here (took me 8min) |
@yegor256 we released a new version. Now it should look like this: |
@h1alexbel I believe, the best format would be a strictly one-sentence message saying: "I would recommend ..." |
@yegor256 you mean drop problems and post only one suggestion? |
@yegor256 how about this? |
@rultor release, tag is |
@h1alexbel OK, I will release it now. Please check the progress here |
@h1alexbel Done! FYI, the full log is here (took me 8min) |
@rultor release, tag is |
@h1alexbel OK, I will release it now. Please check the progress here |
@h1alexbel Done! FYI, the full log is here (took me 7min) |
@yegor256 now should be fixed! |
Take a look at this one: objectionary/eo#3127 (comment)
Such a long report is absolutely useless. Nobody reads it and nobody pays attention. In order to be useful, it has to be short and suggest only one specific improvement to be made. The message should be short (less than 30 words, I believe).
The text was updated successfully, but these errors were encountered: