Thanks for the detailed description of the issue, @CameronBanga! We were able to reproduce it by adding a GitLab repo “manually” (via clone URL). You were right, it was related to how GitLab subgroups are getting handled on our side.
We’ve deployed a fix, so newly added apps won’t be affected. For existing apps though like yours, an admin should reset the repository’s URL on the App Settings page (by changing the URL to something else, saving it, then changing it back.) Sorry for the inconvenience!
After resetting the URL, build status messages should be sent back to GitLab successfully, and the Source button should point to the right URL.
Let us know if it helped!
PS. We were not able to reproduce the GitLab connection issue, subgroups were loaded successfully after connecting a GitLab account to Bitrise. Please try to reconnect your GitLab account on your Bitrise profile page and let us know if the repositories are still not loading.