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
Because this is a static web project, I think we can leverage Netlify's continuous deployment, which can fasten development process.
More precisely, if we have the Netlify integration in place, it can automatically build a new PR and host it on a certain domain that we can directly test before merging the code.
The text was updated successfully, but these errors were encountered:
Hola @heytitle !
At the moment brainweb is sooo static, that it doesn't require any building. And because we are directly using a GitHub page, we don't need deployment.
That said, it'd be good to write some tests. The code base is not too big at the moment, but that should change. In that case, continuous integration would be really helpful. We have no experience with Netlify, we mostly use CircleCI. Now, github also has its own continuous integration stuff, which could be interesting to try :D
Do you have experience writing tests for this kind of software? (it's mostly calls to different APIs...)
Thanks for the reply. Actually, Netlify is more like for viewing changes live.
For example, if I create a PR fixing the hight of the top menu, Netlify will take my code and host it somewhere. So, you can see how the website looks like with my change.
Having said that. it's complement to CircleCI, which I guess it is normally used for regression tests.
Another GitHub Actions that might be helpful for this project:
Hi,
Because this is a static web project, I think we can leverage Netlify's continuous deployment, which can fasten development process.
More precisely, if we have the Netlify integration in place, it can automatically build a new PR and host it on a certain domain that we can directly test before merging the code.
The text was updated successfully, but these errors were encountered: