Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add release notifications #640

Closed
lunny opened this issue Jan 11, 2017 · 7 comments
Closed

Add release notifications #640

lunny opened this issue Jan 11, 2017 · 7 comments
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality type/feature Completely new functionality. Can only be merged if feature freeze is not active.

Comments

@lunny
Copy link
Member

lunny commented 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.

@lunny lunny added type/enhancement An improvement of existing functionality type/feature Completely new functionality. Can only be merged if feature freeze is not active. labels Jan 11, 2017
@lunny lunny added this to the 1.1.0 milestone Jan 11, 2017
@appleboy
Copy link
Member

Nice feature.

@lunny lunny modified the milestones: 1.2.0, 1.1.0 Feb 14, 2017
@lunny
Copy link
Member Author

lunny commented Feb 14, 2017

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

@lunny lunny modified the milestones: 1.x.x, 1.2.0 Apr 20, 2017
@markg85
Copy link

markg85 commented 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.

@stale
Copy link

stale bot commented 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 stale bot added the issue/stale label Jan 11, 2019
@stale
Copy link

stale bot commented Feb 21, 2019

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

@stale stale bot closed this as completed Feb 21, 2019
@techknowlogick techknowlogick added issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented and removed issue/stale labels Feb 21, 2019
@suatfk
Copy link

suatfk commented Jan 19, 2020

if still open can you assign it to me ?

@mrsdizzie
Copy link
Member

Release notification added in #12463

@lunny lunny removed this from the 1.x.x milestone Sep 8, 2020
@suatfk suatfk removed their assignment Oct 4, 2020
@go-gitea go-gitea locked and limited conversation to collaborators Nov 24, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented type/enhancement An improvement of existing functionality type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

No branches or pull requests

6 participants