Should be able to import personal projects

[applejag]

Currently GitLab importer are able to import projects from selected group. When we do not indicate the group it will take all projects that user has access to including personal projects. On the list it is shown as 'username/projectname'. If someone will decide to import only personal projects an error will occur. Things to do:

• add get list personal project functionality to git lab fetcher

• on import group add aditional check if delivered group name is a user name. If it is a group or a username, it should be supplied as a separate input.

• write UT to new functionality

• Changes in frontend should be included in this task

[Alexamakans]

Possibly closed by changes 92052ac and 1c32a44 in #43?

Edit: Per discussion below, not closed by #43.

[applejag]

@Alexamakans Possibly closed by changes 92052ac and 1c32a44 in #43?

Idk, you're the author :P You tell me

[Alexamakans]

@Alexamakans Possibly closed by changes 92052ac and 1c32a44 in #43?

Idk, you're the author :P You tell me

Unsure what is meant by personal projects here, and if it is retrieved differently from "normal" projects or not.
And if the frontend changes have been implemented and whatnot.

Probably should have added that in my previous comment 🦘

[applejag]

@Alexamakans IIRC then this is only an issue when importing projects in Wharf from GitLab with the group specified but not the project name.

For example:

• Importing everything from GitLab group https://gitlab.com/F-Droid works fine ✔️, such as:

  

• Importing everything from GitLab user https://gitlab.com/dwt1 fails ❌, such as:

  

Probably because if not supplying a project name when importing via Wharf, it performs a group project listing, when it instead should be a little smarter and do a user project listing if the specified Wharf group ends up being a GitLab user.

[applejag]

And if the frontend changes have been implemented and whatnot.

That part of the issue description I cannot vouch for. I am not the original author of this issue, as it was a work order that was copied over from our previously used issue tracker/ITSM ("The Cure").

I do not see any need for any frontend changes. Rather that the wharf-provider-gitlab deals with the two alternative Wharf group type abstraction instead of like adding a <select> input field to wharf-web for "GitLab user" contra "GitLab group"