I split testing from build/deploy but it's not correct. The app will be deployed even if it fails the testing yaml file (well, technically it still has to build but it could get past the linter).
It would be better to potentially collapse the yaml files into one flow that tests in a lot of cases (anytime code is pushed to Github) and only attempts to deploy in a smaller set of cases:
- pull request created/updated
master or release branches updated
I split testing from build/deploy but it's not correct. The app will be deployed even if it fails the testing yaml file (well, technically it still has to build but it could get past the linter).
It would be better to potentially collapse the yaml files into one flow that tests in a lot of cases (anytime code is pushed to Github) and only attempts to deploy in a smaller set of cases:
masterorreleasebranches updated