Set up Travis CI to run tools/normalise-json.js for every push, branch and PR.
If JSON(-LD) files are changed in a way that breaks JSON syntax (or “standard” JSON formatting) that push, branch or PR will be marked as “broken”. PRs can still be merged etc (it's just a flag), but ideally we should make a point of paying attention to Travis CI warnings.
To ensure JSON files are okay, simply make sure you always run tools/normalise-json.jsbefore committing your changes, and check its output. Run also git status to see if the script fixed any of the files (in which case, confirm that fix is okay and add it to you commit, too).
Current build status for the main branch is now shown at the top of the README.
Set up Travis CI to run
tools/normalise-json.jsfor every push, branch and PR.If JSON(-LD) files are changed in a way that breaks JSON syntax (or “standard” JSON formatting) that push, branch or PR will be marked as “broken”. PRs can still be merged etc (it's just a flag), but ideally we should make a point of paying attention to Travis CI warnings.
To ensure JSON files are okay, simply make sure you always run
tools/normalise-json.jsbefore committing your changes, and check its output. Run alsogit statusto see if the script fixed any of the files (in which case, confirm that fix is okay and add it to you commit, too).Current build status for the main branch is now shown at the top of the README.