Create basic CircleCI config #47
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Vou abrir outro PR pra ver se resolve o problema do netlify (alteramos algumas configs) |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Esse PR configura o Circle CI para rodar no repositório. Com isso podemos atacar a issue #43.
Tomei a liberdade de trocar o
npmpeloyarnpor todos os benefícios que o yarn traz.Além disso simplifiquei um pouco os scripts de build.
Atualmente, o único "teste" que o CI está fazendo é rodar:
A ideia agora é criar uma suite de testes e substituir esse comando 😉
PS: os deploys do netlify pra
dev.phpspestão falhando. É assim mesmo?Vamos dropar esse ambiente de staging? (se for o caso, já tiro o
stagingdos build scripts)Na minha opinião os deploy previews que o netlify geram já são o suficiente pra testar.