[PR #16] [MERGED] fix: use description for breaking changes if no message in footer #28

New issue

Closed

opened 2026-03-04 00:41:01 +03:00 by kerem · 0 comments

kerem commented

2026-03-04 00:41:01 +03:00

Owner

📋 Pull Request Information

Original PR: https://github.com/thegeeklab/git-sv/pull/16
Author: @xoxys
Created: 10/28/2023
Status: ✅ Merged
Merged: 10/28/2023
Merged by: @xoxys

Base: main ← Head: fix-breaking

📝 Commits (3)

f225819 fix: use description for breaking changes if no message in footer
d7c3560 use uppercase title for breaking changes
009aba9 fix test

📊 Changes

4 files changed (+23 additions, -26 deletions)

View changed files

📝 .gitsv/config.yml (+1 -1)
📝 sv/message.go (+17 -21)
📝 sv/message_test.go (+4 -2)
📝 sv/releasenotes.go (+1 -2)

📄 Description

No description provided

_{🔄 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/thegeeklab/git-sv/pull/16 **Author:** [@xoxys](https://github.com/xoxys) **Created:** 10/28/2023 **Status:** ✅ Merged **Merged:** 10/28/2023 **Merged by:** [@xoxys](https://github.com/xoxys) **Base:** `main` ← **Head:** `fix-breaking` --- ### 📝 Commits (3) - [`f225819`](https://github.com/thegeeklab/git-sv/commit/f2258190795a6c110064de9b3627020c5549416c) fix: use description for breaking changes if no message in footer - [`d7c3560`](https://github.com/thegeeklab/git-sv/commit/d7c3560ea50da7b5eb2aeb920d713b357f7c4e5a) use uppercase title for breaking changes - [`009aba9`](https://github.com/thegeeklab/git-sv/commit/009aba9b0a88b5d7ad59303ecf68c9638662e7d1) fix test ### 📊 Changes **4 files changed** (+23 additions, -26 deletions) <details> <summary>View changed files</summary> 📝 `.gitsv/config.yml` (+1 -1) 📝 `sv/message.go` (+17 -21) 📝 `sv/message_test.go` (+4 -2) 📝 `sv/releasenotes.go` (+1 -2) </details> ### 📄 Description _No description provided_ --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>