Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[HFRONT-1145]: update quartz contributing #670

Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
8 changes: 5 additions & 3 deletions CONTRIBUTING.MD
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Our commits rely on [conventional commits](https://www.conventionalcommits.org/e

Releases are tied to the commit messages via [semantic-release](https://github.com/semantic-release/semantic-release).

Any commit(a PR merge) into `dev`, which is our main branch, is published to NPM under the [`@logicalclocks/quartz` package](https://www.npmjs.com/package/@logicalclocks/quartz).
Any commit(a PR merge) into `dev`, which is our main branch, is published to Github.

## Commit rules

Expand Down Expand Up @@ -44,7 +44,7 @@ The `footer` is optional. The [Commit Message Footer](#commit-footer) format des
│ │ │
│ │ └─⫸ Summary in present tense. Not capitalized. No period at the end.
│ │
│ └─⫸ Commit Scope: animations|bazel|benchpress|common|compiler|compiler-cli|core|
│ └─⫸ Commit Scope: component|animations|bazel|benchpress|common|compiler|compiler-cli|core|
│ elements|forms|http|language-service|localize|platform-browser|
│ platform-browser-dynamic|platform-server|router|service-worker|
│ upgrade|zone.js|packaging|changelog|docs-infra|migrations|ngcc|ve|
Expand All @@ -71,7 +71,7 @@ Must be one of the following:


##### Scope
The scope should be the name of the npm package affected (as perceived by the person reading the changelog generated from commit messages).
The scope should be the name of the npm package or component affected (as perceived by the person reading the changelog generated from commit messages).

The following is the list of supported scopes:

Expand Down Expand Up @@ -117,6 +117,8 @@ We no longer need to specify `width` by hand.

- if the commit header has `feat`, we do a minor release(1.**2**.0)

- if the commit header has `break`, we do a major release(**2**.0.0)

- everything else produces a patch(1.1.**2**)

- if the footer has `BREAKING CHANGE`, then it's major release(**2**.0.0)
2 changes: 1 addition & 1 deletion package.json
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
{
"homepage": "https://github.com/logicalclocks/quartz",
"name": "@logicalclocks/quartz",
"version": "4.10.5",
"version": "4.10.6",
"description": "Logical Clocks Design System Library",
"author": "logicalclocks",
"license": "MIT",
Expand Down