docs: contributing guide details

machadoleonardo · Dec 1, 2018 · a6302b0 · a6302b0
1 parent 0310e0f
commit a6302b0
Showing 1 changed file with 4 additions and 2 deletions.
diff --git a/.github/CONTRIBUTING.md b/.github/CONTRIBUTING.md
@@ -29,13 +29,15 @@ Commit messages should follow the [commit message convention](./COMMIT_CONVENTIO
 
 ### For core contributors
 
-The points below are mostly to simplify code review in a long run.
 * Keep amount of local branches minimal.
 * Always link PR to issue (via `fix #123`).
 * For small issues you may push to `develop` branch directly while adding (`fix #123`) to commit message.
-* Be sure to create single PR for one issue. If we have several PRs - move all code into a single one and close the rest. If one PR covers several issues - either split it in several PRs or mark one of the issues as duplicate.
+* Create single PR for one issue. If we have several PRs - move all the code into a single one and close the rest. If one PR covers several issues - either split it in several PRs or mark one of the issues as duplicate.
 * Be sure to have only one person assigned per issue.
 * Check your code: https://github.com/epicmaxco/vuestic-admin/issues/378.
+* We use [yarn](https://yarnpkg.com/lang/en/) for package management.
+* Be proactive. If you think something is wrong - create an issue or discuss.
+* Recommended tools: [GitKraken](https://www.gitkraken.com/), [WebStorm](https://www.jetbrains.com/webstorm/)
 
 ### Commonly used NPM scripts