oppi.li
1# This file describes the expected reviewers for a PR based on the changed
2# files. Unlike what the name of the file suggests they don't own the code, but
3# merely have a good understanding of that area of the codebase and therefore
4# are usually suited as a reviewer.
5
6
7# Please mind the alphabetic order of reviewers.
8
9# Files related to frontend development.
10
11# Javascript and CSS code.
12web_src/.* @caesar @crystal @gusted
13
14# HTML templates used by the backend.
15templates/.* @caesar @crystal @gusted
16## the issue sidebar was touched by fnetx
17templates/repo/issue/view_content/sidebar.* @fnetx
18
19# Playwright tests
20tests/e2e/.* @fnetx
21
22# Files related to Go development.
23
24# The modules usually don't require much knowledge about Forgejo and could
25# be reviewed by Go developers.
26modules/.* @gusted
27
28# Models has code related to SQL queries, general database knowledge and XORM.
29models/.* @gusted
30
31# The routers directory contains the most amount code that requires a good grasp
32# of how Forgejo comes together. It's tedious to write good integration testing
33# for code that lives in here.
34routers/.* @gusted
35
36# Let locale changes be checked by the translation team.
37options/locale/.* @0ko
38options/locale_next/.* @0ko
39
40# Personal interest
41.*/webhook.* @oliverpool