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

[PR #262] [MERGED] Add more Conventional Commit tools to the list #400

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

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/262
Author: @tunnckoCore
Created: 4/20/2020
Status: ✅ Merged
Merged: 7/27/2020
Merged by: @damianopetrungaro

Base: master ← Head: patch-1

📝 Commits (3)

📊 Changes

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

View changed files

📝 content/v1.0.0/index.md (+4 -0)

📄 Description

They were in previous versions, or at least the "parser" which is much more nowadays than just a parser.

Or should I move them all above? Hm. Anyway, I don't want to aggressively promote or anything, they are just pretty useful for those folks interested in CC. They were born and are used in @standard-release and similar things.

🔄 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/262 **Author:** [@tunnckoCore](https://github.com/tunnckoCore) **Created:** 4/20/2020 **Status:** ✅ Merged **Merged:** 7/27/2020 **Merged by:** [@damianopetrungaro](https://github.com/damianopetrungaro) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (3) - [`8fa2014`](https://github.com/conventional-commits/conventionalcommits.org/commit/8fa2014ce0c8cdfffb41a9564e4305ab422ed9c3) add tools for CC, which exists for years - [`936d97f`](https://github.com/conventional-commits/conventionalcommits.org/commit/936d97f2b87a7657ee6dd41ad2c8c8a709255877) chore: move parser above - [`0b83e04`](https://github.com/conventional-commits/conventionalcommits.org/commit/0b83e04475f4daa567bc7cd083e9c101480a180a) ocd ### 📊 Changes **1 file changed** (+4 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `content/v1.0.0/index.md` (+4 -0) </details> ### 📄 Description They were in previous versions, or at least the "parser" which is much more nowadays than just a parser. Or should I move them all above? Hm. Anyway, I don't want to aggressively promote or anything, they are just pretty useful for those folks interested in CC. They were born and are used in @standard-release and similar things. --- <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 12:02:05 -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#400
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?