Our current GH Actions workflow mirrors a plethora of external and GH-internal repositories into our infrastructure.
The list of mirrored repositories has grown, and it is not clear whether all mirrored repositories are still required for offline development environments, or long-term maintenance purposes.
This creates unnecessary maintenance overhead regarding the synchronization of repositories that may no longer be needed.
Our current GH Actions workflow mirrors a plethora of external and GH-internal repositories into our infrastructure.
The list of mirrored repositories has grown, and it is not clear whether all mirrored repositories are still required for offline development environments, or long-term maintenance purposes.
This creates unnecessary maintenance overhead regarding the synchronization of repositories that may no longer be needed.