github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-13 02:57:44 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

[PR #429] [CLOSED] Notifications - Step 1 #15376

New Issue
Closed
opened 2025-11-02 11:45:10 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 11:45:10 -06:00
Owner
Copy Link

📋 Pull Request Information

Original PR: https://github.com/go-gitea/gitea/pull/429
Author: @andreynering
Created: 12/20/2016
Status: ❌ Closed

Base: master ← Head: notifications-step-1

📝 Commits (3)

  • db33c50 Notifications - Step 1
  • 175b5de Set notification status to read
  • 4501dbc Reduce number of queries for performance

📊 Changes

5 files changed (+340 additions, -11 deletions)

View changed files

📝 models/issue.go (+10 -2)
📝 models/models.go (+34 -9)
➕ models/notification.go (+245 -0)
➕ modules/notification/notification.go (+46 -0)
📝 routers/repo/issue.go (+5 -0)

📄 Description

First step to resolve #145

This deprecates #321

I plan 2 steps:

  • Create database table and create/update notifications (this one)
  • Actually have UI for notifications

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/go-gitea/gitea/pull/429 **Author:** [@andreynering](https://github.com/andreynering) **Created:** 12/20/2016 **Status:** ❌ Closed **Base:** `master` ← **Head:** `notifications-step-1` --- ### 📝 Commits (3) - [`db33c50`](https://github.com/go-gitea/gitea/commit/db33c508854933347f7cc4cb0e84aa74cd4b5d7e) Notifications - Step 1 - [`175b5de`](https://github.com/go-gitea/gitea/commit/175b5debfda5ce0ccb09f0fc992501287d61fe5f) Set notification status to read - [`4501dbc`](https://github.com/go-gitea/gitea/commit/4501dbc5704f9eb2158b47c1babaafb2973f6a17) Reduce number of queries for performance ### 📊 Changes **5 files changed** (+340 additions, -11 deletions) <details> <summary>View changed files</summary> 📝 `models/issue.go` (+10 -2) 📝 `models/models.go` (+34 -9) ➕ `models/notification.go` (+245 -0) ➕ `modules/notification/notification.go` (+46 -0) 📝 `routers/repo/issue.go` (+5 -0) </details> ### 📄 Description First step to resolve #145 This deprecates #321 I plan 2 steps: - [ ] Create database table and create/update notifications (this one) - [ ] Actually have UI for notifications --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
GiteaMirror added the pull-request label 2025-11-02 11:45:10 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#15376
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?