Ignore certain GitHub branches for preview builds? #4086
-
|
With the new hard limit of 640 serverless function deployments per month, I will be pushing to Now less frequently. Can a branch be ignored by Now so it is possible to use GitHub without worrying? Even better can the preview branches be opt-in instead? |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment 1 reply
-
|
Hey @Sever1an, thanks for raising this! We definitely don't want the limits to impact the workflows of our customers. We'll take this feedback and see what we can offer a little further down the line with regards to this. |
Beta Was this translation helpful? Give feedback.
-
|
I can envision changing stuff shared by all of our SSR pages, like the template component, resulting in all of the functions being updated. We never anticipated a penalty for using more SSR pages and made new ones without concern. Some push operations might consume 5, 10, or even a theoretical maximum of 24, from the limit. With a modest number of pages (5) a team can only push 4 times per day. At the extreme (24) a team can only push less than once a day... If the limit were firm, with a self-service forgiveness option, this would be a non-issue. Being completely locked out of development is serious. Completing the next.js function consolidation feature would be a reasonable solution, but we want to be careful until then. Systematically, if these limits help Now to be sustainable, we are quite happy to keep local-testing-only branches. However, they need to be in GitHub. |
Beta Was this translation helpful? Give feedback.
Hey @Sever1an, thanks for raising this! We definitely don't want the limits to impact the workflows of our customers. We'll take this feedback and see what we can offer a little further down the line with regards to this.