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
{{ message }}
This repository has been archived by the owner on Aug 3, 2022. It is now read-only.
Deployable Naming Convention
Under a particular use-case, hundreds of collaborator branches may be generated at any given time. Only a subset of these may require deployment. Is it possible to use or implement pattern matching in a c.get()?
Then in .toml I can use:
[context.'deploy/*']
command = "build command"
Then, ideally:
whatever-*-is.myDomain.com
I don't know whether it would make more sense within "Override with branch context environment" or above it (might be redundant?).
The text was updated successfully, but these errors were encountered:
I'm closing this since the issue is really with the platform, not this library. Feel free to go to https://community.netlify.com. We can track feature requests like this one there.
Deployable Naming Convention
Under a particular use-case, hundreds of collaborator branches may be generated at any given time. Only a subset of these may require deployment. Is it possible to use or implement pattern matching in a c.get()?
Then in .toml I can use:
Then, ideally:
whatever-*-is.myDomain.com
I don't know whether it would make more sense within "Override with branch context environment" or above it (might be redundant?).
The text was updated successfully, but these errors were encountered: