Backwards compatibility checks fail on community contributions
Overview
Looking a jobs like https://gitlab.com/gitlab-org/labkit/-/jobs/1559609693 and https://gitlab.com/gitlab-org/labkit/-/jobs/1559609692 jobs are failing to run from a fork of labkit
!138 (merged) because the commit is not present inside of the gitlab.com/gitlab-org/labkit
but inside of the user repository.
Possible Fixes
- If we can update the
go get
command so that it uses the user namespace instead that might be fix the issue