You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Am a GitHub organization with multiple packages coming from a variety of teams. Some packages still get updates but don't use a common naming pattern across all the packages we push.
I want a single token that I can provide to our GitHub organization secrets to allow pushing these existing packages, but still prevent other packages that don't conform to our convention.
It'd be nice if I could provide a semi-colon delineated list, or provide multiple entries to the glob matching pattern to allow.
Even better if I could configure them for existing packages or new packages as part of the same token.
Additional Context and Details
Otherwise, I have to create multiple tokens and then provide different tokens to different projects instead of being able to have a central token which I can renew periodically to manage our organization.
The text was updated successfully, but these errors were encountered:
Related Problem
Related #8223
The Elevator Pitch
Am a GitHub organization with multiple packages coming from a variety of teams. Some packages still get updates but don't use a common naming pattern across all the packages we push.
I want a single token that I can provide to our GitHub organization secrets to allow pushing these existing packages, but still prevent other packages that don't conform to our convention.
It'd be nice if I could provide a semi-colon delineated list, or provide multiple entries to the glob matching pattern to allow.
Even better if I could configure them for existing packages or new packages as part of the same token.
Additional Context and Details
Otherwise, I have to create multiple tokens and then provide different tokens to different projects instead of being able to have a central token which I can renew periodically to manage our organization.
The text was updated successfully, but these errors were encountered: