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

ignore binary files automatically #1264

Open
yegor256 opened this issue Apr 29, 2024 · 1 comment
Open

ignore binary files automatically #1264

yegor256 opened this issue Apr 29, 2024 · 1 comment

Comments

@yegor256
Copy link
Owner

See #1055

Let's automatically ignore all binary files.

Copy link

@yegor256 thanks for the report, here is a feedback:

Problems

  • Insufficient Details: The report lacks specific details regarding the issue. It remains unclear why the user intends to automatically ignore all binary files.
  • Lack of Reproduction Steps: The report fails to provide steps to reproduce the issue.
  • No Expected versus Actual Results: The report does not delineate the actual outcomes and the anticipated results.

Suggestions

  • Add Detailed Description: Provide more context and detail about the issue. Explain why it's necessary to automatically ignore all binary files, and how this problem impacts the system or the user experience.
  • Include Reproduction Steps: Include a clear, step-by-step guide to reproduce the issue. This can help others understand exactly what you're experiencing and aid in diagnosing the problem.
  • Specify Expected and Actual Results: Clearly define what you expect to happen and what actually happens. This contrast can help highlight the issue and make it easier for others to understand the problem you're facing.
  • Referencing Other Issues: When referencing other issues like 'RegexpSinglelineCheck applies to *.png, *.js, *.css files within the standalone application #1055', make sure to provide a brief summary of that issue in this report, to give readers an idea of the related problem without requiring them to navigate away from the current report.
  • Add Screenshots or Logs if Possible: If it's relevant, add screenshots, error logs, or any other additional information that could provide more context about the issue.
  • Test on Different Environments: If possible, test the issue in different environments (like different operating systems, browsers, devices) and include those details in the report. It helps to understand if the issue is specific to a certain environment or is more widespread.
  • Suggest Impact and Severity: While it's not mandatory, suggesting the impact and severity of the issue might help prioritize the bug fixing process.

Please fix the bug report in order it to get resolved faster.
Analyzed with gpt-4

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

No branches or pull requests

1 participant