{"push_id":3635634911,"size":10,"distinct_size":10,"ref":"refs/heads/develop","head":"3b57ee0d359bb105af88e6c851695627e34845a4","before":"d7d3a0dda55d7cbd5c068105e3cf5a49a4e104c6","commits":[{"sha":"1698284940c73448f8e317a0af0a88468ccc5976","author":{"name":"jrfnl","email":"50d644c256f2863fd67b233efe329d3f54f4e258@users.noreply.github.com"},"message":"CapitalPDangit: ignore misspellings in constant declarations\n\nJust like in array declarations, when `wordpress` is spelled incorrectly in constant declarations, this will be a false positive in 90% of the cases, so just ignore it.\n\nFixes 1698","distinct":true,"url":"https://api.github.com/repos/jrfnl/WordPress-Coding-Standards/commits/1698284940c73448f8e317a0af0a88468ccc5976"},{"sha":"c7dcd238a77995a6a00f7e8953db3e58ad39b0cb","author":{"name":"Gary Jones","email":"64b2b6d12bfe4baae7dad3d018f8cbf6b0e7a044@garyjones.io"},"message":"CapitalPDangit: ignore misspellings in constant declarations (#1699)\n\nCapitalPDangit: ignore misspellings in constant declarations","distinct":true,"url":"https://api.github.com/repos/jrfnl/WordPress-Coding-Standards/commits/c7dcd238a77995a6a00f7e8953db3e58ad39b0cb"},{"sha":"79b68552a94e618525856585f73d837de26aaf32","author":{"name":"jrfnl","email":"50d644c256f2863fd67b233efe329d3f54f4e258@users.noreply.github.com"},"message":"Sniff::is_test_class(): recognize `TestCase`\n\nWhat with WP dropping support for PHP 5.2, I expect that more and more projects will start to use `use` statements in their code.\n\nWhen the PHPUnit native `PHPUnit\\Framework\\TestCase` is imported via a `use` statement and then `extend`ed, the WPCS sniffs would not recognize the extending class as a test class.\n\nAdding `TestCase` to the default test class whitelist fixes this.\n\nWhile this means that any class extending the quite genericly named `TestCase` will now be recognized as a test class, even when the `TestCase` in question is not the PHPUnit native one, I think it's safe to assume that even when it's not the PHPUnit native one, it _will_ be a test base class and for WPCS purposes the extending class can be marked as a test class.\n\nIncludes unit test via the `GlobalVariablesOverride` sniff.\n\nIncludes adjusting an existing unit test for the `FileName` sniff to still test what it was testing before.","distinct":true,"url":"https://api.github.com/repos/jrfnl/WordPress-Coding-Standards/commits/79b68552a94e618525856585f73d837de26aaf32"},{"sha":"3a2f289e36f5a54650d54a53d1d74e11f1c5d6e0","author":{"name":"Gary Jones","email":"64b2b6d12bfe4baae7dad3d018f8cbf6b0e7a044@garyjones.io"},"message":"Sniff::is_test_class(): recognize `TestCase` (#1706)\n\nSniff::is_test_class(): recognize `TestCase`","distinct":true,"url":"https://api.github.com/repos/jrfnl/WordPress-Coding-Standards/commits/3a2f289e36f5a54650d54a53d1d74e11f1c5d6e0"},{"sha":"3aadeeea8b28c3580841c3962e0cb40308519c5b","author":{"name":"jrfnl","email":"50d644c256f2863fd67b233efe329d3f54f4e258@users.noreply.github.com"},"message":"Update default minimum_supported_version to WP 4.9\n\nThe minimum version should be three versions behind the latest WP release, so what with 5.2 being out, it should now be 4.9.\n\nIncludes (not) updating the list of deprecated functions. Input for this based on @JDGrimes's WP deprecated code scanner.","distinct":true,"url":"https://api.github.com/repos/jrfnl/WordPress-Coding-Standards/commits/3aadeeea8b28c3580841c3962e0cb40308519c5b"},{"sha":"4b5091b16c3594af670dcdd25e409e7dc9074f9a","author":{"name":"Gary Jones","email":"64b2b6d12bfe4baae7dad3d018f8cbf6b0e7a044@garyjones.io"},"message":"Update default minimum_supported_version to WP 4.9 (#1708)\n\nUpdate default minimum_supported_version to WP 4.9","distinct":true,"url":"https://api.github.com/repos/jrfnl/WordPress-Coding-Standards/commits/4b5091b16c3594af670dcdd25e409e7dc9074f9a"},{"sha":"97d6fbf1e95215140cf54e229bbfb341b9bd72c4","author":{"name":"Juliette","email":"f41e94a8bfdec9bb972a751e68a37cbdabaa07ea@users.noreply.github.com"},"message":"Changelog for WPCS 2.1.1 (#1707)\n\nChangelog for WPCS 2.1.1\r\n\r\n* Release date set at this **Tuesday May 21st**.\r\n* Includes all currently merged changes.","distinct":true,"url":"https://api.github.com/repos/jrfnl/WordPress-Coding-Standards/commits/97d6fbf1e95215140cf54e229bbfb341b9bd72c4"},{"sha":"0c7aff07ad0a2064588c9e6255bb86dcfb2a5089","author":{"name":"jrfnl","email":"50d644c256f2863fd67b233efe329d3f54f4e258@users.noreply.github.com"},"message":"Travis: run the code style related and ruleset checks in separate stages\n\nTravis now offers stages. Using stages we can:\n- Run the code style related checks before running any unit tests and stop the build early if any are detected.\n- Remove the duplicate unit test runs - i.e. previously we had an extra (third) build against PHP 7.2 (now changed to 7.3) which would run the code style related checks, but would also re-run the unit tests. This extra build will now no longer run the unit tests.\n\nWhile this does mean that the unit tests will run with a slight delay (the `Sniff` and `Rulesets` stages have to finish before they start), it also means that we:\n* Get code style errors reported earlier as it's been moved to be the first stage and the build will just stop if any are found.\n* We won't be wasting Travis's resources on builds which will have to be re-run anyway.\n\nRef: https://docs.travis-ci.com/user/build-stages/\n\nNote that `Allowed failures` is no longer listed as a separate block in the Travis result overview, but is _is_ respected.\n\nFor more discussion about this:\n* https://github.com/travis-ci/travis-ci/issues/7789\n* https://travis-ci.community/t/always-show-allow-failures-allowed-failures-when-build-stages-are-used/217\n* https://travis-ci.community/t/work-out-kinks-in-interactions-between-stages-allow-fail-and-fast-finish/1090\n* https://github.com/travis-ci/travis-ci/issues/9677","distinct":true,"url":"https://api.github.com/repos/jrfnl/WordPress-Coding-Standards/commits/0c7aff07ad0a2064588c9e6255bb86dcfb2a5089"},{"sha":"fc44f79556168cd6204a2c7ef72750b318cee2d1","author":{"name":"Stephen Edgar","email":"06fa905d7f2aaced6dc72e9511c71a2a51e8aead@netweb.com.au"},"message":"Update .travis.yml","distinct":true,"url":"https://api.github.com/repos/jrfnl/WordPress-Coding-Standards/commits/fc44f79556168cd6204a2c7ef72750b318cee2d1"},{"sha":"3b57ee0d359bb105af88e6c851695627e34845a4","author":{"name":"Gary Jones","email":"64b2b6d12bfe4baae7dad3d018f8cbf6b0e7a044@garyjones.io"},"message":"Travis: run the code style related and ruleset checks in separate stages (#1711)\n\nTravis: run the code style related and ruleset checks in separate stages\r\n\r\nCo-authored-by: Stephen Edgar <stephen@netweb.com.au>","distinct":true,"url":"https://api.github.com/repos/jrfnl/WordPress-Coding-Standards/commits/3b57ee0d359bb105af88e6c851695627e34845a4"}]}
{"actor":{"display_login":"jrfnl"}}