Repository structure and CI/CD pipeline for SPFx WebParts

I am currently developing SPFx WebParts for a single SharePoint site. In our development repository, I have:

A shared SPFx library

Six separate WebParts, each in its own solution, organized as follows:

• library
• webparts
  • webpart1
  • webpart2
  • webpart3 ...

At the moment, on Azure DevOps, everything is managed in a single repository. To build and deploy a WebPart, I check Git for changes, build the WebPart, and then deploy it.

I am considering whether, for the CI/CD pipeline, it might be more efficient to adopt a separate repository for each WebPart, allowing independent pipelines for each solution.

In this scenario, I have two main questions:

1. Is it considered a best practice to separate WebParts into distinct repositories?
2. How should the shared SPFx library be managed in this case? I assume it would need a separate repository, but I would like guidance on the best way to integrate it with the WebParts.

Thank you for your support.