For CircleCI to start testing builds on this fork, @kblincoe needs to authorise circleci to access this repo. To do this, log into circleci and click on "Add Projects" in the left sidebar, and find this project. This will start a default (un-configured) build which will fail, but once this PR is merged, the correct configuration will be used. Once this is happened, the build will still fail, but that is because the JS tests are currently failing as of writing.
Steps to test:
Branch off this branch in the kblincoe repository
Commit some failing code, and the PR should indicate a failing status
Fix the failing code, and after committing and pushing the PR should indicate a passing status
fraserdrops
commented
6 years ago
This PR closes issues #143
For CircleCI to start testing builds on this fork, @kblincoe needs to authorise circleci to access this repo. To do this, log into circleci and click on "Add Projects" in the left sidebar, and find this project. This will start a default (un-configured) build which will fail, but once this PR is merged, the correct configuration will be used. Once this is happened, the build will still fail, but that is because the JS tests are currently failing as of writing.
Steps to test: