refactor: evaluate RuleElements with @sindresorhus/ow#isValid#101
Open
gregswindle wants to merge 6 commits intomasterfrom
Open
refactor: evaluate RuleElements with @sindresorhus/ow#isValid#101gregswindle wants to merge 6 commits intomasterfrom
gregswindle wants to merge 6 commits intomasterfrom
Conversation
Production 1. @sindresorhus/is@1.0.0 2. fs-extra@8.1.0 Development 1. @semantic-release/changelog@3.0.4 2. @semantic-release/commit-analyzer@6.3.0 3. @semantic-release/git@7.0.16 4. @semantic-release/github@5.4.3 5. @semantic-release/npm@5.1.15 6. @semantic-release/release-notes-generator@7.3.0 7. all-contributors-cli@6.8.1 8. commitizen@4.0.3 9. coveralls@3.0.6 10. eslint@6.2.2 11. eslint-config-prettier@6.1.0 12. eslint-config-standard@14.0.1 13. eslint-find-rules@3.4.0 14. eslint-plugin-import@2.18.2 15. eslint-plugin-promise@4.2.1 16. eslint-plugin-standard@4.0.1 17. eslint-plugin-unicorn@10.0.0 18. husky@3.0.4 19. jest@24.9.0 20. jest-junit@7.0.0 21. jsdoc@3.6.3 22. lint-staged@9.2.3 23. prettier@1.18.2 24. remark@11.0.1 25. remark-frontmatter@1.3.2 26. remark-lint@6.0.5 27. remark-preset-lint-consistent@2.0.3 28. remark-preset-lint-markdown-style-guide@2.1.3 29. remark-preset-lint-recommended@3.0.3 30. remark-retext@3.1.3 31. retext-english@3.0.3 32. retext-repeated-words@2.0.0 33. retext-sentence-spacing@3.0.0 34. retext-spell@3.0.0 35. retext-syntax-urls@1.0.2 36. rollup@1.20.1 37. rollup-plugin-commonjs@10.0.2 38. rollup-plugin-node-resolve@5.2.0 39. rollup-plugin-terser@5.1.1 40. semantic-release@15.13.24 41. sonarqube-scanner@2.5.0 42. unified@8.3.2 Run - npm audit fix - npm prune - npm dedupe Closes #57 Closes #66 Closes #69 Closes #70 Closes #72 Closes #80 Closes #84 Closes #87 Closes #95 Closes #99
Update dev-dependencies: 1. jest-junit@8.0.0 --save-dev 2. lint-staged@9.2.4 --save-dev 3. rollup@1.20.2 --save-dev Remove unused dev and prod dependencies. \#97
Update dev-dependencies: 1. all-contributors-cli@6.9.0 2. better-docs@1.2.2 3. eslint@6.3.0 4. eslint-config-prettier@6.2.0 5. eslint-config-standard@14.1.0 6. eslint-plugin-node@10.0.0 7. husky@3.0.5 8. lint-staged@9.2.5 9. rollup@1.20.3 10. rollup-plugin-commonjs@10.1.0 \#97
|
Code Climate has analyzed commit b8629f2 and detected 0 issues on this pull request. View more on Code Climate. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
RuleElementoperator methods to use@sindresorhus/ow#isValid.archetypes-rules=>@archetypes/rules.Associated issue(s)
Closes #97
Closes #103
completed, tested, and validated.
require updates.
View the "Code Review Cheat-sheet"...
Rule 1: Review all Code before Releasing it
Do the code reviews before deployment.
Why:
Rule 2: All developers review code
Make sure all your developers get to review code.
Why:
Rule 3: Four-to-Eight (4-8) Hours per Developers per Week
The optimal amount of time to spend on code reviews is between 0.5 to 1 day per
week per developer.
Rule 4: Don't Release Code that Fails Reviews
Make code reviews blocking, that is, don’t deploy before they have been carried
out.
Rule 5: More Rigor, Better Quality and Velocity
Be strict and thorough when reviewing code.
Why:
Code quality summary
Code quality, vulnerability, and standards compliance tools
How to format, lint, and test your changes
Open a Terminal, go to the root directory for archetypes-rules, and run:
$ npm testHow to test a release
The Pre-release test instructions include step-by-step guidelines for bundling, packing, and testing this module as it would be released on NPM.