Skip to content

WIP: Improve notification to include releases notification and notification reason #9118

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

Closed
wants to merge 3 commits into from

Conversation

lunny
Copy link
Member

@lunny lunny commented Nov 22, 2019

  • Refactor notification structs to add notification reason, add release notification source
  • Support release message
  • Classrify messages on UI ( all, watch, subscribe, participats, assignee)

@stale stale bot added the issue/stale label Jan 21, 2020
@GiteaBot GiteaBot added the lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. label Jan 21, 2020
@stale stale bot removed the issue/stale label Jan 21, 2020
@lunny lunny added the issue/confirmed Issue has been reviewed and confirmed to be present or accepted to be implemented label Jan 21, 2020
@lunny lunny force-pushed the lunny/improve_notification branch from 2e3fcf8 to 5f8e7e2 Compare December 23, 2020 09:31
@lunny lunny changed the title WIP: Improve notification to include commits/releases notification WIP: Improve notification to include releases notification and notification reason Dec 23, 2020
@lunny lunny added the type/feature Completely new functionality. Can only be merged if feature freeze is not active. label Dec 23, 2020
@go-gitea go-gitea deleted a comment from stale bot Dec 23, 2020
@lunny lunny force-pushed the lunny/improve_notification branch from 5f8e7e2 to 6e3b71d Compare December 24, 2020 09:46
@lunny
Copy link
Member Author

lunny commented Mar 25, 2023

Closed as too many conflicts.

@lunny lunny closed this Mar 25, 2023
@lunny lunny deleted the lunny/improve_notification branch March 25, 2023 07:42
@go-gitea go-gitea locked and limited conversation to collaborators May 3, 2023
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 lgtm/need 2 This PR needs two approvals by maintainers to be considered for merging. type/feature Completely new functionality. Can only be merged if feature freeze is not active.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants