{"push_id":4053328726,"size":1,"distinct_size":1,"ref":"refs/heads/chore/use-standard-rb","head":"3f7d84f0aa9774f1a821f5f9bbf5e14db2937798","before":"fe6743a73cbf4d6623c4c5909f922cf522b4a276","commits":[{"sha":"3f7d84f0aa9774f1a821f5f9bbf5e14db2937798","author":{"name":"Tom Hipkin","email":"96431c8f741969838c686438f5fdcfe15b9f1fc4@gmail.com"},"message":"Linting checks are run as part of the single rake command\n\n* Having all of our tests run through a single command helps us run tests in all environments in a consistent manner. This will help us catch linting errors in development before our work is merged in. It also removes the need for CI testing commands to stay in sync as we add or remove different tests.\n* The ordering declares that `standard` should be run after `rspec`. The thought process is that early functional feedback is more important than stylistic feedback. We expect rspec failures as a result of TDD and getting a fast feedback cycle is important. Running the linting everytime before rspec can break focus and momentum.\n* The ordering decision can be aided by using editor linting to help make corrections in tandem to avoid a big blob of stylistic fixes at the end. Without this, there is the risk of large trailing commits solely focused on style fixes. The intended behaviour would be to have these contributed in the original commits.","distinct":true,"url":"https://api.github.com/repos/dxw/rails-template/commits/3f7d84f0aa9774f1a821f5f9bbf5e14db2937798"}]}
{"actor":{"display_login":"tahb"}}