Automated Release Notes #8911

New Issue

GiteaMirror · 2025-11-02T08:22:57-06:00

GiteaMirror commented

2025-11-02 08:22:57 -06:00

Originally created by @agsiegel on GitHub (May 5, 2022).

Feature Description

I have recently migrated from Jira/Bitbucket to Gitea. Everything is going very well. There is one feature that I miss. When creating a new release in Jira it automatically puts a list of all the tickets on the projects "completed" Kanban board into the release notes. Something like the following would be sufficient.

#1234: Ticket title
#1235: Ticket title
#1236: Ticket title

The release "Content" field could be auto filled in after clicking the "New Release" button with the tickets listed on a specified Kanban board.

Screenshots

No response

Originally created by @agsiegel on GitHub (May 5, 2022). ### Feature Description I have recently migrated from Jira/Bitbucket to Gitea. Everything is going very well. There is one feature that I miss. When creating a new release in Jira it automatically puts a list of all the tickets on the projects "completed" Kanban board into the release notes. Something like the following would be sufficient. #1234: Ticket title #1235: Ticket title #1236: Ticket title The release "Content" field could be auto filled in after clicking the "New Release" button with the tickets listed on a specified Kanban board. ### Screenshots _No response_

GiteaMirror added the type/proposal type/feature issue/workaround labels 2025-11-02 08:22:57 -06:00

GiteaMirror commented

2025-11-02 08:22:58 -06:00

@bminer commented on GitHub (Apr 27, 2024):

Here's a relevant project for GitHub: https://github.com/github-tools/github-release-notes

@bminer commented on GitHub (Apr 27, 2024): Here's a relevant project for GitHub: https://github.com/github-tools/github-release-notes

GiteaMirror commented

2025-11-02 08:22:58 -06:00

@lunny commented on GitHub (Apr 28, 2024):

You can do that with Gitea Actions.

@lunny commented on GitHub (Apr 28, 2024): You can do that with Gitea Actions.

GiteaMirror commented

2025-11-02 08:22:58 -06:00

@bminer commented on GitHub (Apr 30, 2024):

You can do that with Gitea Actions.

How? Can you provide a link?

@bminer commented on GitHub (Apr 30, 2024): > You can do that with Gitea Actions. How? Can you provide a link?

GiteaMirror commented

2025-11-02 08:22:59 -06:00

@ybizeul commented on GitHub (Mar 20, 2025):

Oddly enough, reviving this issue, as I couldn't find any usable auto release notes solutions for Gitea.

https://github.com/mikepenz/release-changelog-builder-action is unusable with gitea (partially?) because of https://github.com/go-gitea/gitea/issues/33943 and their so-called gitea integration mode seems to be just broken, matching labels with commit contents instead of title in first line.

I didn't give https://github.com/lakto/gren-action a shot yet

@ybizeul commented on GitHub (Mar 20, 2025): Oddly enough, reviving this issue, as I couldn't find any usable auto release notes solutions for Gitea. https://github.com/mikepenz/release-changelog-builder-action is unusable with gitea (partially?) because of https://github.com/go-gitea/gitea/issues/33943 and their so-called gitea integration mode seems to be just broken, matching labels with commit contents instead of title in first line. I didn't give https://github.com/lakto/gren-action a shot yet

GiteaMirror commented

2025-11-02 08:22:59 -06:00

@lunny commented on GitHub (Mar 29, 2025):

Maybe git-sv can help. There is an example here https://gitea.com/gitea/helm-gitea/src/branch/main/.gitea/workflows/changelog.yml

@lunny commented on GitHub (Mar 29, 2025): Maybe git-sv can help. There is an example here https://gitea.com/gitea/helm-gitea/src/branch/main/.gitea/workflows/changelog.yml

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#8911