Variables, Secrets and repository overview to GitHub Teams #112106
Replies: 1 comment
-
I think they should also do team runners too. I work for a company that has lots of repos and teams with in a single org. Giving out Org level access is not good practice. But allowing teams to manage runners across multiple repos makes a lot of since. The teams already have access to add runners, and secrets at each repo level, so the security issue to allow them to manage them at a team level should be minimal. GitHub already has much of what is needed, just in a different setup. Let's take what a Team Level Runner would look like. You can use the same function you already have with Runner Groups at the Org level. These runner groups can be setup to only allow specific repos for the runners. So let's allow teams to also act in that function. Now, let's take a look at what a Team level secret/variable would look like. This too can work a lot like what you use for Org Level secrets, but just at the team level. For a team, under the setting section you would have Secrets and variables and be able to add what we will call "Team Secrets". We use the same function of what every repo is associated with, the team will show the secret in it. For limits, we can do the same as we do for org, If the repository is assigned access to more than 100 team secrets, the workflow can only use the first 100 team secrets. |
Beta Was this translation helpful? Give feedback.
-
Select Topic Area
Product Feedback
Body
Having the Teams in GitHub bring a useful way of assigning permissions. However, It would be more useful to get additional functionality to those Teams, such as repository lists(code responsibility/ownership) and common secrets and variables.
This would allow us to minimize the repeatability of adding common secrets/variables of the Team and an overview of the team repositories.
We are currently using "custom properties" to add the repository per team functionality.
Beta Was this translation helpful? Give feedback.
All reactions