Sha256: 91ea8a58ca390a752a3ea6aa48d6a9f47fabd279691d11fcf34dd443e0a79865
Contents?: true
Size: 712 Bytes
Versions: 2
Compression:
Stored size: 712 Bytes
Contents
= RuboCop Committee Committee-specific analysis for your projects, as an extension to https://github.com/rubocop/rubocop[RuboCop]. RuboCop Committee follows the https://docs.rubocop.org/rubocop/versioning.html[RuboCop versioning guide]. In a nutshell, between major versions new cops are introduced in a special `pending` status. That means that they won’t be run unless explicitly told otherwise. RuboCop will warn on start that certain cops are neither explicitly enabled and disabled. On a major version release, all `pending` cops are enabled. == Project Goals * Enforce the style of the test code to be best practice when using committee * Simplify the process of adopting new Committee functionality
Version data entries
2 entries across 2 versions & 1 rubygems
Version | Path |
---|---|
rubocop-committee-0.1.1 | docs/modules/ROOT/pages/index.adoc |
rubocop-committee-0.1.0 | docs/modules/ROOT/pages/index.adoc |