Add release notifications #219

New Issue

GiteaMirror · 2025-11-02T03:14:22-06:00

GiteaMirror commented

2025-11-02 03:14:22 -06:00

Originally created by @lunny on GitHub (Jan 11, 2017).

I suppose add a new notification when a new release published. All watched user could receive a release notification via UI or mail. This could be an option for user, default is true.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Originally created by @lunny on GitHub (Jan 11, 2017). I suppose add a new notification when a new release published. All watched user could receive a release notification via UI or mail. This could be an option for user, default is true. <bountysource-plugin> --- Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/40827935-add-release-notifications?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F47456670&utm_medium=issues&utm_source=github). </bountysource-plugin>

GiteaMirror added the issue/confirmed type/feature type/enhancement labels 2025-11-02 03:14:22 -06:00

GiteaMirror closed this issue

2025-11-02 03:14:23 -06:00

GiteaMirror commented

2025-11-02 03:14:23 -06:00

@appleboy commented on GitHub (Jan 11, 2017):

Nice feature.

@appleboy commented on GitHub (Jan 11, 2017): Nice feature.

GiteaMirror commented

2025-11-02 03:14:24 -06:00

@lunny commented on GitHub (Feb 14, 2017):

Since #765 has moved to v1.2, let's move this one also.

@lunny commented on GitHub (Feb 14, 2017): Since #765 has moved to v1.2, let's move this one also.

GiteaMirror commented

2025-11-02 03:14:24 -06:00

@markg85 commented on GitHub (Sep 6, 2018):

+1 for this feature. I just had a need for this for another project on github and ended up using gitpunch.
You could choose to not add this and stay compatible with how the release rss looks so that gitpunch also works in gitea.

Still, would be nice if this would be a build-in feature to not rely on a external service for release notifications.

@markg85 commented on GitHub (Sep 6, 2018): +1 for this feature. I just had a need for this for another project on github and ended up using gitpunch. You could choose to not add this and stay compatible with how the release rss looks so that gitpunch also works in gitea. Still, would be nice if this would be a build-in feature to not rely on a external service for release notifications.

GiteaMirror commented

2025-11-02 03:14:24 -06:00

@stale[bot] commented on GitHub (Jan 11, 2019):

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

@stale[bot] commented on GitHub (Jan 11, 2019): This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs during the next 2 weeks. Thank you for your contributions.

GiteaMirror commented

2025-11-02 03:14:24 -06:00

@stale[bot] commented on GitHub (Feb 21, 2019):

This issue has been automatically closed because of inactivity. You can re-open it if needed.

@stale[bot] commented on GitHub (Feb 21, 2019): This issue has been automatically closed because of inactivity. You can re-open it if needed.

GiteaMirror commented

2025-11-02 03:14:24 -06:00

@suatfk commented on GitHub (Jan 19, 2020):

if still open can you assign it to me ?

@suatfk commented on GitHub (Jan 19, 2020): if still open can you assign it to me ?

GiteaMirror commented

2025-11-02 03:14:24 -06:00