Skip to content

More flexible environment variable wildcard scopes #6316

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
chuck-alt-delete opened this issue Oct 20, 2021 · 2 comments
Closed

More flexible environment variable wildcard scopes #6316

chuck-alt-delete opened this issue Oct 20, 2021 · 2 comments
Labels
meta: stale This issue/PR is stale and will be closed soon team: webapp Issue belongs to the WebApp team

Comments

@chuck-alt-delete
Copy link

chuck-alt-delete commented Oct 20, 2021

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.

@stale
Copy link

stale bot commented Jan 19, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

@stale stale bot added the meta: stale This issue/PR is stale and will be closed soon label Jan 19, 2022
@axonasif axonasif added the team: webapp Issue belongs to the WebApp team label Jan 22, 2022
@stale stale bot removed the meta: stale This issue/PR is stale and will be closed soon label Jan 22, 2022
@stale
Copy link

stale bot commented Apr 24, 2022

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
meta: stale This issue/PR is stale and will be closed soon team: webapp Issue belongs to the WebApp team
Projects
None yet
Development

No branches or pull requests

2 participants