-
Notifications
You must be signed in to change notification settings - Fork 1.3k
Environment Variables and org/rep #1358
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
It's not entirely clear to me what you mean by “folder structure”. I guess you mean nested groups / subgroups like Indeed I can confirm that setting env vars in a nested group does not work with |
Thx @corneliusludmann that was exactly what I meant ;-) |
Any chance this can get through to the SaaS offering of GitPod soon? This issue stops me from using it. |
It is deployed now. |
This doesn't seem to be fixed, see -> #8618 (comment) |
Describe the bug
If you have folders in gitlab.com, like // the environment variable created after a gp env foo=bar will be /, but if you do a gp env -e you are not getting the variables back, because your repo is in //, the only workaround so far is to use / in Org/rep in settings.
Steps to reproduce
Add a folder structure in gitlab and you reproduce the bug
The text was updated successfully, but these errors were encountered: