github-starred/conventionalcommits.org
2
0
Fork 0
mirror of https://github.com/conventional-commits/conventionalcommits.org.git synced 2026-03-23 06:01:43 -05:00
Code Issues 153 Packages Projects Releases Wiki Activity

[PR #15] [CLOSED] feat(specs): rewrite spec of syntax #243

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

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/15
Author: @robinpokorny
Created: 7/20/2017
Status: ❌ Closed

Base: master ← Head: rewrite-syntax

📝 Commits (1)

  • d478963 feat(specs): rewrite specs of syntax

📊 Changes

1 file changed (+14 additions, -15 deletions)

View changed files

📝 index.md (+14 -15)

📄 Description

The current spec has several formal ambiguities:

  • Point 1. does not (formally) allow scope.
  • Examples of scope and description include type.
  • feat is not a verb.
  • Unclear what ‘type/scope prefix’ is.

I tried to remove these and I hope this change achieves that.

Do you think it is OK? Is it readable?

🔄 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/15 **Author:** [@robinpokorny](https://github.com/robinpokorny) **Created:** 7/20/2017 **Status:** ❌ Closed **Base:** `master` ← **Head:** `rewrite-syntax` --- ### 📝 Commits (1) - [`d478963`](https://github.com/conventional-commits/conventionalcommits.org/commit/d47896376cd5608ca1193aa8160d11d0f43c9ac9) feat(specs): rewrite specs of syntax ### 📊 Changes **1 file changed** (+14 additions, -15 deletions) <details> <summary>View changed files</summary> 📝 `index.md` (+14 -15) </details> ### 📄 Description The current spec has several formal ambiguities: * Point 1. does not (formally) allow scope. * Examples of scope and description include type. * `feat` is not a verb. * Unclear what ‘type/scope prefix’ is. I tried to remove these and I hope this change achieves that. Do you think it is OK? Is it readable? --- <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:38 -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#243
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?