Derzeit ist es nicht möglich Gitlab via HTTPS per lokalem Benutzernamen und Passwort zu benutzen. Wir empfehlen allen Nutzenden als Sofortmaßnahme ein Personal Access Token anstatt Benutzername und Passwort zu verwenden. Eine Anleitung zur Erstellung eines Personal Access Token finden Sie hier: https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html // It is currently not possible to use Gitlab via HTTPS with a local username and password. As an immediate measure, we recommend that all users use a personal access token instead of a username and password. You can find instructions on how to create a personal access token here: https://docs.gitlab.com/ee/user/profile/personal_access_tokens.html
The implementation of #49 (closed) explicitly only handles variables of the FIRST struct encountered.
!52 (merged) can cause the entries to be reordered, in case of nested structs
The effort to handle multiple structs is not too big. So why not cover this, in case users' workflows organize the data in such a way?