themadbit opened a new issue, #8827:
URL: https://github.com/apache/incubator-devlake/issues/8827

   ### Search before asking
   
   - [x] I had searched in the 
[issues](https://github.com/apache/incubator-devlake/issues?q=is%3Aissue) and 
found no similar issues.
   
   
   ### What happened
   
   When adding scope to the GitLab connection, if there are multiple repos with 
the same name, all repos are populated with the same name, and this makes it 
impossible to tell which exact repo I want to add to a project.
   
   <img width="739" height="108" alt="Image" 
src="https://github.com/user-attachments/assets/a0af87be-a6d2-4a3d-84cf-2d4d54c20b4e";
 />
   
   ### What do you expect to happen
   
   When adding repos to the GitLab connection, if there's an already existing 
repo with that name, the user should be prompted to take an action. Rename the 
repo from their source, rename the repo as  devlake, will reference it, or, 
when a user is choosing the repo to add, it should show the full path of the 
repo. 
   
   NB: This happens because GitLab has groups and subgroups that might have 
repos with the same name. 
   
   ### How to reproduce
   
   Have to repos with the same name and add them to the GitLab Connection.
   Create a project.
   Add scopes to the project.
   When adding the repo scopes, you'll see both named correctly
   It will be difficult to tell which repo you want for this project
   
   ### Anything else
   
   _No response_
   
   ### Version
   
   v1.0.3-beta10@99376a8
   
   ### Are you willing to submit PR?
   
   - [ ] Yes I am willing to submit a PR!
   
   ### Code of Conduct
   
   - [x] I agree to follow this project's [Code of 
Conduct](https://www.apache.org/foundation/policies/conduct)
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to