github-starred/conventionalcommits.org
2
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2026-03-22 12:44:37 -05:00
Code Issues 153 Packages Projects Releases Wiki Activity

conventional commits support in https://github.com/evidencebp/commit-classification #113

New Issue
Open
opened 2026-02-17 11:47:23 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2026-02-17 11:47:23 -06:00
Owner
Copy Link

Originally created by @evidencebp on GitHub (Nov 10, 2020).

I'd like to submit a classifier that supports conventional commits.
The commit-classification repository supply natural language processing model in order to classify commit messages.
Such analysis is vital for software engineering research (e.g., the use of corrective commit probability for code quality analysis) and usually very hard.

Conventional commits is a promise to make such analysis simpler and more accurate (humans reach ~95% accuracy in commit classification).
I added the text analysis here.
Text file of test is here.
Labeling protocols (accepting conventional commits if appearing) are here.

I'll be happy to get feedback.

Originally created by @evidencebp on GitHub (Nov 10, 2020). I'd like to submit a classifier that supports conventional commits. The [commit-classification](https://github.com/evidencebp/commit-classification) repository supply natural language processing model in order to classify commit messages. Such analysis is vital for software engineering research (e.g., the use of [corrective commit probability](https://arxiv.org/pdf/2007.10912.pdf) for code quality analysis) and usually very hard. Conventional commits is a promise to make such analysis simpler and more accurate (humans reach ~95% accuracy in commit classification). I added the text analysis [here](https://github.com/evidencebp/commit-classification/blob/master/conventional_commits.py). Text file of test is [here](https://github.com/evidencebp/commit-classification/blob/master/data/conventional_commits.csv). Labeling protocols (accepting conventional commits if appearing) are [here](https://github.com/evidencebp/commit-classification/tree/master/labeling_protocols). I'll be happy to get feedback.
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#113
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?