Add user-wide secrets for Actions

[hwittenborn]

I currently use Drone CI, and the one thing that I really love about it is the ability to use user-wide secrets.

This is probably one of the sole reasons I'm avoiding Actions for my builds, as needing to add the same secret to multiple repositories quickly becomes tedious as the number of repositories starts to rise.

Any chance secrets could be allowed on a per-user level?

[rajbos]

You know you can set them at the organization level, right? Still want to have them for a user as well, or even a team level: that would help as well and saves you the hassle of using them on the organization level and then adding each repo that can use it to the allow list of the secret.

[hwittenborn]

Yep, I was wanting to use secrets on a user-wide level.

[leighmcculloch]

The organization level feature is great for organizations, but for repositories not associated with an organization, there is no way to specify a secrets that can be used across multiple repositories.

[leighmcculloch]

This is probably one of the sole reasons I'm avoiding Actions for my builds

Much the same for me migrating Google Cloud Build builds to Actions. The prospect of having to manage private keys for Google Cloud across a dozen GitHub repos, rather than manage a single auth with Google Cloud, is pretty scary.

[hwittenborn]

Exactly! It's not even necessarily that it's tedious to initially add keys, but rather just much more so when I need to change their values, where it can get chaotic real quick.

[WeihanLi]

I used to use the Azure DevOps pipelines, it has a variable group feature, it would let me manage my secrets across different pipelines.
Currently, there's the organization secret, maybe we could have a user secret too?
Really hope for that, thanks.

[Badisi]

Now that npm is enforcing new token lifetime limits, this missing feature requires me to frequently manually update my npm token across all my GitHub projects, which is quite cumbersome..

[hwittenborn]

Spam 🙅‍♂️