Currently if the VCS URL redirects or invalid (404) we get a logging message, but the report still indicates that the module has a VCS.
It might also indicate the lack of CI if the VCS url is incorrect. That can be confusing
We should probably indicate that it the VCS URL was incorrect. That can only happen if the cloning was successful.
That still can be the wrong repository, but I don't think we need to try to automatically verify that.
Currently if the VCS URL redirects or invalid (404) we get a logging message, but the report still indicates that the module has a VCS. It might also indicate the lack of CI if the VCS url is incorrect. That can be confusing
We should probably indicate that it the VCS URL was incorrect. That can only happen if the cloning was successful. That still can be the wrong repository, but I don't think we need to try to automatically verify that.