github-starred/conventionalcommits.org
2
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2026-05-23 14:20:55 -05:00
Code Issues 1.7k Packages Projects Releases Wiki Activity

Add commit type recommendations with examples as an own block #105

New Issue
Closed
opened 2026-02-17 11:46:19 -06:00 by GiteaMirror · 1 comment
GiteaMirror commented 2026-02-17 11:46:19 -06:00
Owner
Copy Link

Originally created by @Zerotask on GitHub (Jul 13, 2020).

At the moment there are just the 2 mandatory commit types fix and feat. Personally I also follow the recommended other commit types from point 4

  1. Others: commit types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends chore:, docs:, style:, refactor:, perf:, test:, and others.

There is an external link to the Angular convention which shows a better overview of the recommended commit types.

grafik

My suggestion is to add a block (Recommended commit types), similar to that from the Angular convention to the definition (index.md) to give a short summary / explanation of each recommended commit type

Originally created by @Zerotask on GitHub (Jul 13, 2020). At the moment there are just the 2 mandatory commit types **fix** and **feat**. Personally I also follow the recommended other commit types from point 4 > 4. Others: commit types other than fix: and feat: are allowed, for example @commitlint/config-conventional (based on the Angular convention) recommends chore:, docs:, style:, refactor:, perf:, test:, and others. There is an external link to the Angular convention which shows a better overview of the recommended commit types. ![grafik](https://user-images.githubusercontent.com/20150243/87296909-d65bba00-c507-11ea-9f45-3522f5d7a534.png) My suggestion is to add a block (**Recommended commit types**), similar to that from the Angular convention to the definition (index.md) to give a short summary / explanation of each recommended commit type
GiteaMirror commented 2026-02-17 11:46:20 -06:00
Author
Owner
Copy Link

@damianopetrungaro commented on GitHub (Jul 16, 2020):

Looks like #283
We can discuss it there tho :)
Love this one tho, amazing idea @Zerotask !

@damianopetrungaro commented on GitHub (Jul 16, 2020): Looks like #283 We can discuss it there tho :) Love this one tho, amazing idea @Zerotask !
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
discussion
enhancement
greenkeeper
help wanted
meeting-agenda
operations
process
pull-request
Mirrored from GitHub Pull Request
 question
suggestion
support
triaged
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/conventionalcommits.org#105
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?