gitforge/routers
limiting-factor 5b618cabd0 chore(documentation): explain the purpose of routers/api/v1/permissions (#13277)
Refs forgejo/design#63

### Documentation

- [ ] I created a pull request [to the documentation](https://codeberg.org/forgejo/docs) to explain to Forgejo users how to use this change.
- [x] I did not document these changes and I do not expect someone else to do it.

### Release notes

- [ ] This change will be noticed by a Forgejo user or admin (feature, bug fix, performance, etc.). I suggest to include a release note for this change.
- [x] This change is not visible to a Forgejo user or admin (refactor, dependency upgrade, etc.). I think there is no need to add a release note for this change.

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/13277
Reviewed-by: Mathieu Fenniak <mfenniak@noreply.codeberg.org>
2026-07-03 04:58:02 +02:00
..
api chore(documentation): explain the purpose of routers/api/v1/permissions (#13277) 2026-07-03 04:58:02 +02:00
common feat: remove no-transform in Cache-Control header. (#12905) 2026-06-03 05:38:47 +02:00
install feat: replace repo based server-side hooks with centralised hooks (#10397) 2026-04-27 22:34:46 +02:00
private fix: ensure runners either belong to owner or repo when updated (#13262) 2026-07-01 03:49:07 +02:00
utils
web fix(ui): in the admin config panel do not report a cache taking more than 100 microseconds as slow (#13256) 2026-06-30 12:06:06 +02:00
init.go fix: compliance with [migrations].ALLOWED_DOMAINS, ...BLOCKED_DOMAINS, and ....ALLOW_LOCALNETWORKS for git & LFS ops (#13129) 2026-06-23 23:40:25 +02:00