A painful tool to make developer's life harder.
With violence you have to make a set of code style and linting config files to check your code base as a package and use it in every project you want to check.
Used packages inside: eslint, jscs, git-hooks.
On installation it makes (or updates) current hooks and configuration files, creates git hook for checking files and commit messages on precommit (with git-hooks), etc.
Run in your project root to quick start:
npm i violence violence-default --save-devInstall violence package via npm:
npm install violence --save-dev
Enjoy your pain!
- File an issue with properly described suggestion or problem;
- Decide which presets or rules your issue affects;
- Create a feature-branch with an issue number (
issues/<issue_number>). E.g. for an issue 42 it will looks likeissues/42; - Commit changes with a proper message in Angular Commit Message Format, e.g.:
<type>(<scope>): <subject>
<BLANK LINE>
<body>
<BLANK LINE>
<footer>
- Push and make a pull-request from your feature-branch.
- Link your pull request with an issue number any way you like (if you forget to do it in commit message). A comment will work perfectly.
- Wait for your pull request and the issue to be closed 馃樇.
Code and documentation copyright 2015 The Protein Corp. Code released under The MIT License.