dependencies:
  post:
    - npm run build

deployment:
  staging:
    branch: master
    heroku:
      appname: cs1332qna

machine:
  # Ruby version specified in .ruby-version
  node:
    version: 7.5.0

test:
  override:
    # Generate junit xml reports that can be read by CircleCI
    - bundle exec rake test TESTOPTS="--ci-dir=$CIRCLE_TEST_REPORTS/reports":
        parallel: true
        files:
          - test/**/*_test.rb

dependencies:
  post:
    - npm run build

machine:
  # Ruby version specified in .ruby-version
  node:
    version: 7.5.0

test:
  override:
    # Generate junit xml reports that can be read by CircleCI
    - bundle exec rake test TESTOPTS="--ci-dir=$CIRCLE_TEST_REPORTS/reports":
        parallel: true
        files:
          - test/**/*_test.rb

Disable CircleCI deployment to Heroku
Disable CircleCI deployment to Heroku

Heroku is capable of doing it itself. This has the added advantage of
not having the build fail due to git-related errors if Heroku is
currently deployed to a branch other than master.
