gitforge/services/user
christopher-besch 8770ffc848 feat: granular settings for watched repo units (#10927)
Continuation of #10598
Closes #7254

Implement repo granular watch selection

I adopted a lot of the frontend from #10598 while redoing the entire back-end. I propose this new model:
- Remove the WatchMode enum.
- Add the WatchSelection struct, which represents the granular selection. Notice that there is no `watching` bool. I tried very hard to keep the structure as simple and redundancy-free as possible. Therefore, people not watching a repo at all either don't have a watch record or one with an entirely unselected WatchSelection struct.
- Add the WatchSource enum. It replaces the WatchMode enum and has a single purpose: determine whether a watch was explicitly or automatically initiated.

Notice that replacing this
```go
		And("`watch`.mode<>?", WatchModeDont).
```
with this is correct:
```go
		And(
			builder.Or(
				builder.Eq{"`watch`.watch_selection_issues": true},
				builder.Eq{"`watch`.watch_selection_pull_requests": true},
				builder.Eq{"`watch`.watch_selection_releases": true},
			),
		).
```
That's because there are four modes: dont, none, auto and normal. When `<>` with dont, we look for auto and normal, because there are no records with none. Therefore, the old code looks for records that indicate watching. The code I replaced this with does so, too, just more granular.

Also notice that I've prepared a future `user preset` in a few places. See below for a little more info on that.

## Next PR
I plan to continue working on this. I want to implement a `user preset` option. The user sets that `user preset` in her settings and may use them in any repo.
<details>
- rename account settings to account and notifications
- user preset (always use this preset for newly accessible repos (according to AutoWatchOnChanges and AutoWatchNewRepos))
</details>

## Further PRs
- make api able to granular watch
- move (email) notifications to new notifications tab

Co-authored-by: 0ko <0ko@noreply.codeberg.org>
Co-authored-by: Gusted <postmaster@gusted.xyz>
Co-authored-by: pat-s <patrick.schratz@gmail.com>
Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/10927
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
2026-07-09 19:51:10 +02:00
..
TestDeleteUser fix: cascade deletion of a user to their authorized integrations (#13323) 2026-07-06 15:05:11 +02:00
TestDeleteUserCleansUpBranchProtectionRules fix: replace bad pagination to cleanup branch protection rules on user delete (#9833) 2025-10-24 08:49:53 +02:00
TestPurgeUser Do not rewrite ssh keys files when deleting a user without one (#6097) 2024-12-05 21:32:09 +00:00
TestReplaceInactivePrimaryEmail chore: add delete old auth token unit test 2025-08-30 09:54:38 +02:00
avatar.go fix: re-uploading the same avatar doesn't delete it (#12823) 2026-05-30 13:25:36 +02:00
avatar_test.go fix: re-uploading the same avatar doesn't delete it (#12823) 2026-05-30 13:25:36 +02:00
block.go feat: cancel all pull requests runs when blocking a user 2025-11-06 11:07:39 +01:00
block_test.go feat: granular settings for watched repo units (#10927) 2026-07-09 19:51:10 +02:00
delete.go feat: granular settings for watched repo units (#10927) 2026-07-09 19:51:10 +02:00
email.go feat: Add admin individual user email management endpoints (#9594) 2025-10-28 15:52:37 +01:00
email_test.go chore: ensure consistent import aliasing for services and models (#10253) 2025-11-30 17:00:57 +01:00
update.go refactor: replace Value() from Option[T] with Get() & ValueOrZeroValue() (#11218) 2026-02-10 16:41:21 +01:00
update_test.go fix(ui): fall back to default theme from non-existent (#13110) 2026-06-17 19:18:09 +02:00
user.go fix: reflect allowed username change in profile setting (#11171) 2026-02-06 17:47:30 +01:00
user_test.go chore: fix typos throughout the codebase (#10753) 2026-01-26 22:57:33 +01:00