forgejo/CODEOWNERS
Line: 10: incorrect codeowner user: dachary Line: 10: incorrect codeowner user: earl-warren Line: 10: no users/groups matched Line: 15: incorrect codeowner user: caesar Line: 15: incorrect codeowner user: gusted Line: 18: incorrect codeowner user: caesar Line: 18: incorrect codeowner user: gusted Line: 24: incorrect codeowner user: dachary Line: 24: incorrect codeowner user: earl-warren Line: 24: incorrect codeowner user: gusted Line: 24: no users/groups matched Line: 27: incorrect codeowner user: dachary Line: 27: incorrect codeowner user: earl-warren Line: 27: incorrect codeowner user: gusted Line: 27: no users/groups matched Line: 32: incorrect codeowner user: dachary Line: 32: incorrect codeowner user: earl-warren Line: 32: incorrect codeowner user: gusted Line: 32: no users/groups matched
Gusted 52e863ba5a
[META] Add CODEOWNERS files
- As per https://codeberg.org/forgejo/discussions/issues/53#issuecomment-1070207
- Using the `CODEOWNERS` feature it should speed up the development
process for contributors as for the most common PRs the right reviewers
will be added by Forgejo automatically. They can be added very
precisely according to the changed files of the PR.
- This feature is implemented in v1.21, which means it's not available
on Codeberg.

(cherry picked from commit 1511ef1c803f31fcf2887611982a114465f3be60)
(cherry picked from commit 99999e3a03)
(cherry picked from commit 0b0dd6f7a95ce718c8ff73e8e6fe1b660a4e3277)
(cherry picked from commit d42940034f7fe1f1f706e4fff8f9b5c8465003fc)
(cherry picked from commit 5be6e7d2542e6915d1df3d9f29a8504f851b8f52)
(cherry picked from commit d12d6e8633a9f88c1283a3613f8dc1ffff1acacb)
(cherry picked from commit d3b3e691bfad6713b92ee636ddba953b897bfbbd)
(cherry picked from commit 2a13f95551b323a52ea20823760b5ecdc629233a)
(cherry picked from commit 6d882ede35b29f613ab625c16cc5a7ffd7fcc393)
(cherry picked from commit 7c8d754ac6e444aff9acdc6cff1a4270947aeeb0)
(cherry picked from commit 842000a586)
(cherry picked from commit 40d49b5107)
(cherry picked from commit b446a99335)
(cherry picked from commit 6600fa86c3)
(cherry picked from commit 1d16607db5)
(cherry picked from commit ee5da9318bfffff339b8866a87be454c24246fac)
(cherry picked from commit 49e033cec8e924b21c84a20eca213321891ecd11)
(cherry picked from commit 9bca34ef03)
(cherry picked from commit 59c0454c2125baae0427d7ce2c3d698c25ad65cd)
(cherry picked from commit be081bca694d6822a604fe017fe93c4fb1a51308)
2024-02-05 14:44:33 +01:00

33 lines
1.1 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 the CI of the Forgejo project.
.forgejo/.* @dachary @earl-warren
# Files related to frontend development.
# Javascript and CSS code.
web_src/.* @caesar @crystal @gusted
# HTML templates used by the backend.
templates/.* @caesar @crystal @gusted
# Files related to Go development.
# The modules usually don't require much knowledge about Forgejo and could
# be reviewed by Go developers.
modules/.* @dachary @earl-warren @gusted
# Models has code related to SQL queries, general database knowledge and XORM.
models/.* @dachary @earl-warren @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/.* @dachary @earl-warren @gusted