-
Notifications
You must be signed in to change notification settings - Fork 167
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
Make it possible to check the result of PRs #66
Comments
instead it could be nice to put the result in a subfolder in gh pages and post a message on the github issue to go to http://webclient.prismarine.js.org/PR_number/ this would need:
|
Another solution could be to use a service that already has this feature like netlify, vercel, cloudflare pages, ... |
Took a quick look and all of those seem to be paid over a certain number of minutes. During times this repo is most active, we can have 5 PRs being worked on concurrently, each with around 6 commits a day. Each one takes 5 minutes to build (which may be an underestimate since they probably provide underpowered VMs), leading to 4,500 build minutes. That’s way above any of their limits.On Wed, Aug 25, 2021 at 03:53, David Duarte ***@***.***> wrote:
Another solution could be to use a service that already has this feature like netlify, vercel, cloudflare pages, ...
—You are receiving this because you are subscribed to this thread.Reply to this email directly, view it on GitHub, or unsubscribe.
|
I don't think it's a big issue, because if the limit is exceeded it will juste make the pr preview unavailable. If needed all of thoose services have open source plans For netlify you can also not rely on build minutes if you use the github action https://github.com/netlify/actions, but it's more work |
put html code in an artifact on PRs will allow testing before merging
The text was updated successfully, but these errors were encountered: