fix(repo list): fix project group filtering reliability (#7615)

Description

The issue was that the previous implementation relied on the group search which could match multiple groups. This was accounted for by manually filtering on FullPath; however what was not covered was pagination. If the group with the correct fullpath was not on the first page of results, it would result in "No group matching path .." error. The fix is to use the group detail endpoint instead. Also fixes the test data as the full path of groups does not include a leading /

Related Issues

Resolves #7615 (closed)

How has this been tested?

Tested by running (and fixing) the included test suite, and tested on our private gitlab instance where filtering on a specific group lead to the "No group matching path .." error. With these changes it returned the correct result for all of our group filters.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Documentation
  • Chore (Related to CI or Packaging to platforms)
  • Test gap
Edited by 🤖 GitLab Bot 🤖

Merge request reports

Loading