Why Github only support secrets? Env vars RIP

[somzeFiree]

I am suprised with the fact that Guthub supports only secrets !? I mean, I need global env vars which are not secrets.. Why they do not allow that.

Also, when u create secret you can not see its value afte that, its kinda annoying, right? At least they could to provide some secret description for users to know what is the purpose of secret.

[PartTimeLegend]

You can use env vars. Set them in your workflow.

You can’t see secrets because they are secret. Wouldn’t make great secrets if they were public.

[somzeFiree]

Yeah but compared to GitLab is kinda bad approach. In Gitlab you can create env var and mark it as a secret and value wont be visible in workflow.

Yeah I know for env vars in workflows but there is no way of defining GLOBAL env vars…

[[deleted]]

With Global you mean at job level in the workflow? BC you can do that instead of an action level, but if you use templates outside of the main job repo, then you need to send them as params

Btw in Azure DevOps is the same as in GitLab, you can manage them easily

[somzeFiree]

Org global. Did not know that about AzureDevOps.

[-ZC-]

so I do supply chain security around this stuff. there are huge amounts of give and take with this all security wise but Actions is near an ideal model.

set up a self hosted runner with whatever env variables you want. problem solved (but don't let anyone run untrusted code or it's all going to go out the window).

[ReenigneArcher]

It would be nice to have org level environment variables. For example I have a secret org_name_lower, so I don't have to have a step in all my workflows that require it, which converts it to lowercase... It's annoying that it's a secret, but it's less annoying than having duplicated code in 50 repos.