More flexible environment variable wildcard scopes #6316
Labels
meta: stale
This issue/PR is stale and will be closed soon
team: webapp
Issue belongs to the WebApp team
Right now, I can do */*, */{repo}, or {org}/{repo}, but I’d like to do something like {org}/{repo prefix}-* to scope my variables for all repos in an org that start with {repo prefix}.
My particular use case is education. I’d like for my learners to be able to enter environment variables once and have them available in all repos prefixed with
training-
so they only have to do a one time environment variable setup in order to run all training material. Scoping to the prefix is preferable because it’s a large org and people might want different values for those variables in other parts of the org.I realize there could be overlapping scopes, so there would have to be precedence rules, like whichever variables are higher in the list under settings -> variables would get precedence.
The text was updated successfully, but these errors were encountered: