Skip to content

feat: Nested group urls with Gitlab #626

@knubbbe

Description

@knubbbe

Describe the feature

Hey! Thanks for making this cool project!

I have run into an issue with using repositories in nested groups on Gitlab.
For example, we have a component repository with the path https://gitlab.com/<company>/projects/<group>/components.
Since it only searchs for https://gitlab.com/<owner>/<repo>/ right now, it's impossible for us to use the nested repo.
And if we put our component repository in https://gitlab.com/<company>/components we can't add all the members that needs access to it because of Gitlab security restrictions.

Is there any specific reason why only /<owner>/<repo> is used?
Would is be possible touse nested group urls?

I'm happy to help if I can! Not too used to Github workflow though :)

Validations

  • I have checked other issues to see if my feature was already requested or added

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions