EPIC: Detect and Visualize Pull Request Bad Practices

[iam-flo]

Is your feature request related to a problem? Please describe.

Pull requests often exhibit bad practices that hinder collaboration and code quality in software development. Common issues include prolonged open pull requests, excessively large changes, missing or incomplete test coverage, and ambiguous or unclear pull request descriptions. These bad practices make it harder for teams to maintain efficiency, introduce technical debt, and create barriers for novice developers to learn and adapt to proper workflows. There is currently no automated mechanism to consistently identify and flag these issues, leaving them to be addressed through inconsistent and subjective manual oversight.

Describe the solution you'd like

An automated system to detect bad practices in pull requests. The system would analyze pull request data and flag issues such as:
Pull requests left open for too long without updates or progress.
Pull requests containing excessively large changes, making them difficult to review effectively.
Pull requests missing adequate test coverage or test updates.
Pull requests with ambiguous, incomplete, or unstructured descriptions.
The system should provide actionable feedback directly within GitHub to help developers identify and address these issues. This tool would promote better pull request practices, streamline workflows, and reduce technical debt.

Tasks

• Visualize pull requests description bad practices in a dashboard #199
  • Scan and detect bad practices in pull requests on a schedule
    • Pull request description
  • Visualize pull request bad practices in dashboard combined with pull requests
• Detect more bad practices
  • Pull request status
  • Pull request time
  • Pull request changes
• Detect bad practices in realtime(faster than schedule)
• Calculate and visualize pull request metrics in dashboard
• Detect pull request metrics bad practice trends(allow to show trend for bad practices without concrete open PR)
  • Tendency to leave pull requests open too long
  • Tendency to have too short descriptions
• Visualize trends in dashboard
• Add suggestions how to fix or improve bad practices/habits