Secrets on Team and Organization level

[antonb-via]

Hi,

I think it's a good idea to be able to define Secrets not only on repo level, but also on Team and Organization level to avoid duplication between repositories. 

[TopBilly]

Need help. First and maybe last

[chrispat]

Thank you for the feedback.  This is something that is on our backlog for a future update.

[jameskleeh]

This would be a tremendous improvement for us. We have many repositories under our org that we would like to switch to actions from travis. Having to specify half a dozen secrets on every repo would be painful.

[andrejpetras]

Could you be more specific? Release plan?

[ffMathy]

Any progress on this? Can we get an ETA and/or a status update?

[crazy-max]

This behavior is already available for issue and support template, as well as funding through org-wide `.github` repository like this one. I have started to work on a GitHub action to handle org-wide "labelling management" through a simple JSON definition but there is no org-wide events for now. So for the moment I will use GitHub API. Keep you in touch when I've got something stable.

[ZebraFlesh]

Documentation suggests that this only applies to public repos within an organzation. Is the documentation accurate?

[mpdude]

We need secrets like AWS credentials on a larger number of repos. Having team/org secrets would be a *huge* improvement when it comes to rotating keys/credentials, so 👍🏻

[mooreatv]

yes please - and at the "author" level for authors (ie have secrets somewhere in https://github.com/settings/profile that would apply to any repositories I have)