docs aren't building

[EverlastingBugstopper]

from the build logs (the last line seems most relevant) - my guess is something is wrong with the way we use the ignore field in netlify.toml. the docs seem to think that it should be a command that has an exit code of 1 or 0 to tell netlify whether or not to trigger the build.

i think that a PR for this was just merged up the other day and the intent was to fix the badge status in the README.

10:02:20 AM: Failed during stage 'Reading and parsing configuration files': 
{
  "siteInfo": {
    "id": "1646a37a-eb2b-48e8-b6c9-cd074f02bb50"
  },
  "configPath": "/opt/build/repo/netlify.toml",
  "buildDir": "/opt/build/repo/docs",
  "config": {
    "plugins": [],
    "build": {
      "environment": {
        "BRANCH": "avery/move-api",
        "CONTEXT": "deploy-preview",
        "DEPLOY_PRIME_URL": "https://deploy-preview-114--apollo-cli-docs.netlify.app",
        "DEPLOY_URL": "https://5fd8ddf49dc35e0007822d2e--apollo-cli-docs.netlify.app",
        "GO_VERSION": "1.14.4",
        "NETLIFY_IMAGES_CDN_DOMAIN": "d33wubrfki0l68.cloudfront.net",
        "REVIEW_ID": "114",
        "SITE_ID": "1646a37a-eb2b-48e8-b6c9-cd074f02bb50",
        "SITE_NAME": "apollo-cli-docs",
        "URL": "https://apollo-cli-docs.netlify.app"
      },
      "publish": "/opt/build/repo/docs/public",
      "command": "gatsby build --prefix-paths && mkdir -p docs/rover && mv public/* docs/rover && mv docs public/ && mv public/docs/rover/_redirects public",
      "commandOrigin": "config",
      "base": "/opt/build/repo/docs",
      "ignore": false
    }
  },
  "context": "deploy-preview",
  "branch": "avery/move-api"
}

: json: cannot unmarshal bool into Go struct field extendedBuildConfig.Config.build.ignore of type string

[lrlna]

From netlify logs, it seems like the docs haven't been building for a while now. @EverlastingBugstopper do you remember the last time they worked (I only went back as far as Nov 18)?

[EverlastingBugstopper]

they worked for a short while after merging this PR. you can see those here

also just yesterday they published what we had on main here

[abernix]

This was my fault trying to fix another artifact of the Netlify builds which was being reflected via the [Netlify Status Failing] badge on the README. Should be fixed via b028dfe.