Update notifications #414

New Issue

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

GiteaMirror commented

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

Originally created by @pgaskin on GitHub (Mar 2, 2017).

There should be a notification or a system message when an update is available. If on a released version, then when a new version is available. On a master commit, it should show when more than 10 commits are added.

Originally created by @pgaskin on GitHub (Mar 2, 2017). There should be a notification or a system message when an update is available. If on a released version, then when a new version is available. On a master commit, it should show when more than 10 commits are added.

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

GiteaMirror closed this issue

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

GiteaMirror commented

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

@lunny commented on GitHub (Mar 2, 2017):

Do you mean #518 ?

@lunny commented on GitHub (Mar 2, 2017): Do you mean #518 ?

GiteaMirror commented

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

@pgaskin commented on GitHub (Mar 2, 2017):

Yes.

@pgaskin commented on GitHub (Mar 2, 2017): Yes.

GiteaMirror commented

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

@stale[bot] commented on GitHub (Feb 15, 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 (Feb 15, 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:22:37 -06:00

@NotAFile commented on GitHub (Feb 15, 2019):

This would still be a great idea

@NotAFile commented on GitHub (Feb 15, 2019): This would still be a great idea

GiteaMirror commented

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

@stale[bot] commented on GitHub (Apr 16, 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 (Apr 16, 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:22:38 -06:00

@6543 commented on GitHub (Sep 7, 2020):

if implemented, it should be able to disable this with compile flag (for gitea instances deployed by package managers)

@6543 commented on GitHub (Sep 7, 2020): if implemented, it should be able to disable this with compile flag (for gitea instances deployed by package managers)

GiteaMirror commented

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

@fnetX commented on GitHub (Dec 14, 2022):

This can be closed.

@fnetX commented on GitHub (Dec 14, 2022): This can be closed.

GiteaMirror referenced this issue

2025-11-02 11:44:59 -06:00

[PR #414] [CLOSED] Please check the following: #15367

Sign in to join this conversation.