How about non issue commit? #9

New Issue

GiteaMirror · 2026-02-17T11:31:20-06:00

GiteaMirror commented

2026-02-17 11:31:20 -06:00

Originally created by @unional on GitHub (Jul 21, 2017).

e.g commits for version bump, update dependencies, update readme etc?

Should they also consider as fix?

Originally created by @unional on GitHub (Jul 21, 2017). e.g commits for version bump, update dependencies, update readme etc? Should they also consider as `fix`?

GiteaMirror closed this issue

2026-02-17 11:31:21 -06:00

GiteaMirror commented

2026-02-17 11:31:22 -06:00

@stevemao commented on GitHub (Jul 21, 2017):

version bump, update dependencies

chore

update readme

docs

Its not mentioned here?

@stevemao commented on GitHub (Jul 21, 2017): > version bump, update dependencies `chore` > update readme `docs` Its not mentioned here?

GiteaMirror commented

2026-02-17 11:31:23 -06:00

@unional commented on GitHub (Jul 21, 2017):

I see.

I have created a PR, IMO put it on the list make it easier to follow, as people would look for all types in the same section. 🌷

@unional commented on GitHub (Jul 21, 2017): I see. I have created a PR, IMO put it on the list make it easier to follow, as people would look for all types in the same section. 🌷

GiteaMirror commented

2026-02-17 11:31:24 -06:00

@jameswomack commented on GitHub (Aug 2, 2017):

Echoing @stevemao, Unleash creates a commit with the format chore(release): <insert release name here> <insert semantic version here> for releases, e.g. chore(release): release 1.6.1.

I've always used chore with a tag for those sorts of tasks because that's what the Angular team did, as well as the early conventional commit helper packages.

@jameswomack commented on GitHub (Aug 2, 2017): Echoing @stevemao, [Unleash](https://github.com/netflix/unleash) creates a [commit](https://github.com/Netflix/unleash/commit/d0d89ca7046cc0f33359e53fc78f2c22e1b6b827) with the format `chore(release): <insert release name here> <insert semantic version here>` for releases, e.g. `chore(release): release 1.6.1`. I've always used `chore` with a tag for those sorts of tasks because that's what the Angular team did, as well as the early conventional commit helper packages.

GiteaMirror commented

2026-02-17 11:31:24 -06:00

@daKmoR commented on GitHub (Oct 2, 2017):

hmm a release is actually something big right?
so why is it not
RELEASE: 1.2.3 ?
chore(release): 1.2.3 seems pretty small in comparison?

@daKmoR commented on GitHub (Oct 2, 2017): hmm a release is actually something big right? so why is it not `RELEASE: 1.2.3` ? `chore(release): 1.2.3` seems pretty small in comparison?

GiteaMirror commented

2026-02-17 11:31:26 -06:00

@stevemao commented on GitHub (Oct 2, 2017):

@daKmoR I don't think I understand your question?

chore(release): 1.2.3 (or maybe chore(release): publish v1.0.0? see https://github.com/lerna/lerna/blob/master/README.md#--message--m-msg) is a great message for release. However for monorepo, since there's no single version, I use chore(release): publish (https://github.com/conventional-changelog/conventional-changelog/blob/master/package.json)

@stevemao commented on GitHub (Oct 2, 2017): @daKmoR I don't think I understand your question? `chore(release): 1.2.3` (or maybe `chore(release): publish v1.0.0`? see https://github.com/lerna/lerna/blob/master/README.md#--message--m-msg) is a great message for release. However for monorepo, since there's no single version, I use `chore(release): publish` (https://github.com/conventional-changelog/conventional-changelog/blob/master/package.json)

GiteaMirror commented

2026-02-17 11:31:27 -06:00

@zanona commented on GitHub (Nov 20, 2017):

Hey guys,
I have noticed that Angular convention no longer mentions about chore, it seems refactor would be the one being used in its place? and yet many places still use chore.
I know this is all optional and depends on personal/team opinion, but do you guys know why has it been replaced/disappeared and what is the best way to still tag trivial updates, like text changes in websites, or something that would work as a feat neither a fix and yet refactor is not the right word.

Thanks in advance.

@zanona commented on GitHub (Nov 20, 2017): Hey guys, I have noticed that Angular convention no longer mentions about `chore`, it seems `refactor` would be the one being used in its place? and yet many places still use `chore`. I know this is all optional and depends on personal/team opinion, but do you guys know why has it been replaced/disappeared and what is the best way to still tag trivial updates, like text changes in websites, or something that would work as a `feat` neither a `fix` and yet `refactor` is not the right word. Thanks in advance.

GiteaMirror referenced this issue

2026-02-17 11:55:30 -06:00

[PR #11] [MERGED] feat: enable BREAKING with all types #240

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#9