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

[PR #68] [MERGED] fix: add spec compliant parser #275

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

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/68
Author: @tunnckoCore
Created: 7/25/2018
Status: ✅ Merged
Merged: 7/31/2018
Merged by: @damianopetrungaro

Base: master ← Head: patch-1

📝 Commits (1)

  • 9de52db docs: add spec compliant parser

📊 Changes

1 file changed (+1 additions, -0 deletions)

View changed files

📝 spec/v1.0.0-beta.2.md (+1 -0)

📄 Description

It was in work for few months, but last night i released v2 of it. I'm using conventional commits for year or two, and thanks for that specification. I also have badge to the spec in most of my repos.

Let me know if something is not okey.

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/conventional-commits/conventionalcommits.org/pull/68 **Author:** [@tunnckoCore](https://github.com/tunnckoCore) **Created:** 7/25/2018 **Status:** ✅ Merged **Merged:** 7/31/2018 **Merged by:** [@damianopetrungaro](https://github.com/damianopetrungaro) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (1) - [`9de52db`](https://github.com/conventional-commits/conventionalcommits.org/commit/9de52dbb23a87e02819c41f01838a5055a46f4c4) docs: add spec compliant parser ### 📊 Changes **1 file changed** (+1 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `spec/v1.0.0-beta.2.md` (+1 -0) </details> ### 📄 Description It was in work for few months, but last night i released v2 of it. I'm using conventional commits for year or two, and thanks for that specification. I also have badge to the spec in most of my repos. Let me know if something is not okey. --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2026-02-17 11:57:02 -06:00
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 pull-request
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#275
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?