[RFC] Split each project into their own repository

[Justinzobel]

I have used dependabot and shared-modules on several projects, and it is a great initiative.

However, currently shared-modules is one big blog of modules that dependabot updates regularly, often with no benefit to the app using it.

Someone notified me of the schedule feature in dependabot, but this can still create Pull Requests for apps that have no benefit, just less often.

If each module was given its own repository, this would allow projects to use each repository and get valuable updates only when that specific repository was updated.

This results in less GitHub actions run and relevant PRs for app maintainers.

[TingPing]

often with no benefit to the app using it.

But what is the harm?

I think it will just lead to more overhead for those maintaining this and lead to outdated and forgotten repos.

[Erick555]

The harm is eternal spam of updates that have zero relevance for the app which wastes everyone time and CI resources. I think the solution is making update tools able to do differentiate between modules rather than splitting the repo into dozens of pieces though. AFAIK something is done in that regard in f-e-d-c.