Conversation
| # `include`), whether to only display output if it fails (via `quiet`), etc. | ||
| # | ||
| # For a complete list of hooks, see: | ||
| # https://github.com/brigade/overcommit/tree/master/lib/overcommit/hook |
tessie
left a comment
There was a problem hiding this comment.
Please Tag the Issue in commit. And Also update the Readme
|
|
||
|
|
||
|
|
||
| PostCheckout: |
There was a problem hiding this comment.
@Nimmyjv What all are the default postcheckout hooks. Can you please comment here?
Its good to keep just bare minimum
There was a problem hiding this comment.
BowerInstall
BundleInstall
ComposerInstall
IndexTags
NpmInstall
SubmoduleStatus
YarnInstall
| # https://github.com/brigade/overcommit#configuration | ||
| # | ||
| # Uncomment the following lines to make the configuration take effect. | ||
|
|
There was a problem hiding this comment.
Enable hooks for CommitMessage Also
There was a problem hiding this comment.
most of the commit message hooks are enabled by default
| TrailingWhitespace: | ||
| enabled: true | ||
|
|
||
| RubyLint: |
There was a problem hiding this comment.
How is RubyLint and Rubocop different?
There was a problem hiding this comment.
Ruby-lint primarily focuses on logic related errors such as the use of non-existing variables instead of focusing on semantics (e.g. the amount of characters per line).
Rubylint is a sub-analyzer of rubocop.
There was a problem hiding this comment.
@Nimmyjv Do we need to keep both? I felt we just need only ruby-lint
| enabled: true | ||
| command: ['bundle', 'exec', 'ruby-lint'] | ||
|
|
||
|
|
There was a problem hiding this comment.
I dint get it.. format means?
There was a problem hiding this comment.
Please fix the format of yml file. Remove extra lines, etc
No description provided.