Skip to content

Latest commit

 

History

History
93 lines (63 loc) · 1.88 KB

README.md

File metadata and controls

93 lines (63 loc) · 1.88 KB

IS216.023

Requirements

For building and running the application you need:

Run the application locally

Install the dependencies:

npm install

Run the app in development environment:

npm run dev

Use a browser to navigate to http://localhost:3000/.

How to name a branch?

Branch name pattern:

type/description-in-kebab-case

type/issue-#{issue_number}

Examples:

feature/issue-#99
hotfix/quick-fix-for-an-emergency

Common types according to simplified convention for naming branches

  • feature: adding, refactoring or removing a feature
  • bugfix: fixing a bug
  • hotfix: changing code with a temporary solution and/or without following the usual process (usually because of an emergency)
  • test: experimenting outside of an issue/ticket

How to name a commit message?

Commitlint checks if your commit messages meet the conventional commit format.

Commit message pattern:

type(scope?): subject  #scope is optional; multiple scopes are supported (current delimiter options: "/", "\" and ",")

Examples:

chore: run tests on travis ci
fix(server): send cors headers
feat(blog): add comment section

Common types according to commitlint-config-conventional (based on the Angular convention) can be:

  • build
  • chore
  • ci
  • docs
  • feat
  • fix
  • perf
  • refactor
  • revert
  • style
  • test

References

Read these references if needed: