Skip to content

Latest commit

 

History

History
90 lines (52 loc) · 2.91 KB

README.md

File metadata and controls

90 lines (52 loc) · 2.91 KB
Raw

supermarket-scrapper-front

setup project

npm install --force

Conventional Commits

  • init: First commit of the project.

  • finish: Last commit of the project.

  • fix: A commit of the type fix patches a bug in your codebase (this correlates with PATCH in Semantic Versioning).

  • feat: A commit of the type feat introduces a new feature to the codebase (this correlates with MINOR in Semantic Versioning).

  • triangular_flag_on_post: Add, update, or remove feature flags. Not to be counfoused with :feat:, this emoji shoud be used while creating and developing the new feature, and :feat: when this new feature is ready to be merge into the main branch.

  • BREAKING CHANGE: A commit that has a footer BREAKING CHANGE:, or appends a ! after the type/scope, introduces a breaking API change (correlating with MAJOR in Semantic Versioning). A BREAKING CHANGE can be part of commits of any type.

  • style: Improve structure / format of the code.

  • refactor: Refactor code.

  • docs: Add or update documentation.

  • arch: Architecture change.

Examples

a. Commit message with description and breaking change footer

feat: allow provided config object to extend other configs

BREAKING CHANGE: `extends` key in config file is now used for extending other config files

b. Commit message with ! to draw attention to breaking change

feat!: send an email to the customer when a product is shipped

c. Commit message with scope and ! to draw attention to breaking change

feat(api)!: send an email to the customer when a product is shipped

d. Commit message with both ! and BREAKING CHANGE footer

chore!: drop support for Node 6

BREAKING CHANGE: use JavaScript features not available in Node 6.

e. Commit message with no body

docs: correct spelling of CHANGELOG

f. Commit message with scope

feat(lang): add polish language

g. Commit message with multi-paragraph body and multiple footers

fix: prevent racing of requests

Introduce a request id and a reference to latest request. Dismiss
incoming responses other than from latest request.

Remove timeouts which were used to mitigate the racing issue but are
obsolete now.

Reviewed-by: Z
Refs: #123

Create a commit

npm run commit

Emoji for type commit

Commit Type Emoji
fix 🐛
feat ✨
BREAKING CHANGE 💥
style 🎨
refactor ♻️
init 🎉
finish 🚀
docs 📝
arch 🏗️
build 🚩