gitforge/routers/api/v1
forgejo-backport-action 30b5ea66bc [v16.0/forgejo] feat: granular settings for watched repo units (#13385)
**Backport:** https://codeberg.org/forgejo/forgejo/pulls/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: #10927
Reviewed-by: Gusted <gusted@noreply.codeberg.org>
(cherry picked from commit 8770ffc848)
2026-07-09 20:56:52 +02:00
..
activitypub [v16.0/forgejo] chore(refactor): add getter/setter to APIContext data members (#13213) 2026-06-27 18:27:57 +02:00
admin [v16.0/forgejo] chore(refactor): add getter/setter to APIContext data members (#13213) 2026-06-27 18:27:57 +02:00
misc [v16.0/forgejo] chore(refactor): add getter/setter to APIContext data members (#13213) 2026-06-27 18:27:57 +02:00
notify [v16.0/forgejo] chore(refactor): add getter/setter to APIContext data members (#13213) 2026-06-27 18:27:57 +02:00
org [v16.0/forgejo] chore(refactor): add getter/setter to APIContext data members (#13213) 2026-06-27 18:27:57 +02:00
packages [v16.0/forgejo] chore(refactor): add getter/setter to APIContext data members (#13213) 2026-06-27 18:27:57 +02:00
permissions [v16.0/forgejo] chore(refactor): clarify REST API permissions tests (#13271) (#13312) 2026-07-06 00:11:53 +02:00
repo [v16.0/forgejo] fix(api): return empty slice instead of null from the branches API if the repository is empty (#13310) 2026-07-05 04:34:56 +02:00
settings chore: branding import path (#7337) 2025-03-27 19:40:14 +00:00
shared fix: introduce lint-single-response to prevent control flow continuing past a ctx.Error(...)-style method (#13087) 2026-06-14 17:06:03 +02:00
swagger feat(api): add REST API endpoints for Actions artifacts (#12140) 2026-04-20 05:10:54 +02:00
user [v16.0/forgejo] feat: granular settings for watched repo units (#13385) 2026-07-09 20:56:52 +02:00
utils [v16.0/forgejo] chore(refactor): add getter/setter to APIContext data members (#13213) 2026-06-27 18:27:57 +02:00
api.go [v16.0/forgejo] chore(refactor): add getter/setter to APIContext data members (#13213) 2026-06-27 18:27:57 +02:00