Skip to content

feat:added bad mrs option and used asyncro io

Praveena Veeranki requested to merge feature-final into dev

What does this MR do?

This merge request refactors the project to use asynchronous (async I/O) and concurrent execution instead of sequential processing, improving performance and scalability.

It also introduces a BAD MRs batch analysis feature with Excel report generation and cleans up unnecessary UI elements for better clarity.

Motivation / Use Case

Previously:

  • API calls were executed sequentially → slow performance
  • Batch processing for multiple users was inefficient
  • User Profile Overview had unnecessary compliance sections
  • No structured way to analyze bad merge requests in bulk

This MR solves these issues by:

  • Enabling parallel API calls using async I/O

Merge request reports