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

[PR #21] [MERGED] feat: added examples to the specification #248

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

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/21
Author: @tchaffee
Created: 10/11/2017
Status: ✅ Merged
Merged: 4/9/2018
Merged by: @bcoe

Base: master ← Head: feat/add-examples

📝 Commits (1)

  • 197c1eb feat: added examples to the specification

📊 Changes

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

View changed files

📝 index.md (+28 -0)

📄 Description

I was pointed to the specification and wanted to just get started, which would have been possible with examples. Instead I did a lot of reading about the motivation for the spec, and the formal spec itself. I am hoping the examples will help other people see how simple the spec is and to just get started quickly.

🔄 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/21 **Author:** [@tchaffee](https://github.com/tchaffee) **Created:** 10/11/2017 **Status:** ✅ Merged **Merged:** 4/9/2018 **Merged by:** [@bcoe](https://github.com/bcoe) **Base:** `master` ← **Head:** `feat/add-examples` --- ### 📝 Commits (1) - [`197c1eb`](https://github.com/conventional-commits/conventionalcommits.org/commit/197c1eb1bb672679e236b82e19f0fcc9f7aab5fc) feat: added examples to the specification ### 📊 Changes **1 file changed** (+28 additions, -0 deletions) <details> <summary>View changed files</summary> 📝 `index.md` (+28 -0) </details> ### 📄 Description I was pointed to the specification and wanted to just get started, which would have been possible with examples. Instead I did a lot of reading about the motivation for the spec, and the formal spec itself. I am hoping the examples will help other people see how simple the spec is and to just get started quickly. --- <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:55:50 -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#248
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?