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 #117] [MERGED] fix(faq): correct typo #297

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

📋 Pull Request Information

Original PR: https://github.com/conventional-commits/conventionalcommits.org/pull/117
Author: @vicrep
Created: 1/24/2019
Status: ✅ Merged
Merged: 2/18/2019
Merged by: @damianopetrungaro

Base: master ← Head: patch-1

📝 Commits (2)

  • 590f53f fix(faq): correct typo
  • 2c4d85e Merge branch 'master' into patch-1

📊 Changes

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

View changed files

📝 content/next/index.md (+1 -1)

📄 Description

Both are technically correct so might not be a typo, but IMO my suggestion is a clearer way to express this (putting the persona on the project/product as a whole, instead of on the developer).

🔄 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/117 **Author:** [@vicrep](https://github.com/vicrep) **Created:** 1/24/2019 **Status:** ✅ Merged **Merged:** 2/18/2019 **Merged by:** [@damianopetrungaro](https://github.com/damianopetrungaro) **Base:** `master` ← **Head:** `patch-1` --- ### 📝 Commits (2) - [`590f53f`](https://github.com/conventional-commits/conventionalcommits.org/commit/590f53f7998f2e712f817060b76a1f545cebfafb) fix(faq): correct typo - [`2c4d85e`](https://github.com/conventional-commits/conventionalcommits.org/commit/2c4d85e23f632d28a8c15479d941a6a31970decd) Merge branch 'master' into patch-1 ### 📊 Changes **1 file changed** (+1 additions, -1 deletions) <details> <summary>View changed files</summary> 📝 `content/next/index.md` (+1 -1) </details> ### 📄 Description Both are technically correct so might not be a typo, but IMO my suggestion is a clearer way to express this (putting the persona on the project/product as a whole, instead of on the developer). --- <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:56 -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#297
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?