forgejo/CODEOWNERS
Line: 12: incorrect codeowner user: beowulf Line: 12: incorrect codeowner user: gusted Line: 12: no users/groups matched Line: 13: incorrect codeowner user: 0ko Line: 13: no users/groups matched Line: 16: incorrect codeowner user: beowulf Line: 16: incorrect codeowner user: gusted Line: 16: no users/groups matched Line: 18: incorrect codeowner user: fnetx Line: 18: no users/groups matched Line: 21: incorrect codeowner user: fnetx Line: 21: no users/groups matched Line: 27: incorrect codeowner user: gusted Line: 27: no users/groups matched Line: 30: incorrect codeowner user: gusted Line: 30: no users/groups matched Line: 35: incorrect codeowner user: gusted Line: 35: no users/groups matched Line: 38: incorrect codeowner user: 0ko Line: 38: no users/groups matched Line: 39: incorrect codeowner user: 0ko Line: 39: no users/groups matched Line: 42: incorrect codeowner user: fogti Line: 42: no users/groups matched Line: 43: incorrect codeowner user: fogti Line: 43: no users/groups matched Line: 44: incorrect codeowner user: fogti Line: 44: no users/groups matched Line: 47: incorrect codeowner user: oliverpool Line: 47: no users/groups matched Line: 50: incorrect codeowner user: Cyborus Line: 50: no users/groups matched Line: 51: incorrect codeowner user: Cyborus Line: 51: no users/groups matched Line: 52: incorrect codeowner user: Cyborus Line: 52: no users/groups matched Line: 53: incorrect codeowner user: Cyborus Line: 53: no users/groups matched
Cyborus 25eb3f640a add myself to CODEOWNERS for the API (#10160)
I have been looking at this part of the codebase a lot lately, and have spent plenty of time using the API for a while now. I feel I have a good understand of it, and also have interest in keeping up with changes to it, so would like to be added as a `CODEOWNER` for it. :)

Reviewed-on: https://codeberg.org/forgejo/forgejo/pulls/10160
Reviewed-by: Otto <otto@codeberg.org>
Co-authored-by: Cyborus <cyborus@cyborus.xyz>
Co-committed-by: Cyborus <cyborus@cyborus.xyz>
2025-11-18 23:19:39 +01:00

53 lines
1.5 KiB
Text

# This file describes the expected reviewers for a PR based on the changed
# files. Unlike what the name of the file suggests they don't own the code, but
# merely have a good understanding of that area of the codebase and therefore
# are usually suited as a reviewer.
# Please mind the alphabetic order of reviewers.
# Files related to frontend development.
# Javascript and CSS code.
web_src/.* @beowulf @gusted
web_src/css/.* @0ko
# HTML templates used by the backend.
templates/.* @beowulf @gusted
## the issue sidebar was touched by fnetx
templates/repo/issue/view_content/sidebar.* @fnetx
# Playwright tests
tests/e2e/.* @fnetx
# Files related to Go development.
# The modules usually don't require much knowledge about Forgejo and could
# be reviewed by Go developers.
modules/.* @gusted
# Models has code related to SQL queries, general database knowledge and XORM.
models/.* @gusted
# The routers directory contains the most amount code that requires a good grasp
# of how Forgejo comes together. It's tedious to write good integration testing
# for code that lives in here.
routers/.* @gusted
# Let locale changes be checked by the translation team.
options/locale/.* @0ko
options/locale_next/.* @0ko
# lint-locale-usage
build/lint-locale-usage/.* @fogti
models/unit/.* @fogti
services/migrations/lint-locale-usage/.* @fogti
# Personal interest
.*/webhook.* @oliverpool
# Often work with, and on, the API
modules/structs/.* @Cyborus
routers/api/v1/.* @Cyborus
routers/api/forgejo/.* @Cyborus
tests/integration/api_.* @Cyborus