-
Notifications
You must be signed in to change notification settings - Fork 0
/
CODEOWNERS
Validating CODEOWNERS rules...
26 lines (24 loc) · 1.67 KB
/
CODEOWNERS
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
###############################################################################
# GitHub Code-owner Configuration for Navigator Backend
#
# Each line is a file pattern followed by one or more owners. See this link:
# https://docs.github.com/en/repositories/managing-your-repositorys-settings-and-features/customizing-your-repository/about-code-owners#example-of-a-codeowners-file
# for more information on configuring GitHub code owners, including examples.
###############################################################################
# These owners will be the default owners for everything in
# the repo. Unless a later match takes precedence, members
# of @climatepolicyradar/software will be requested for
# review when someone opens a pull request. Teams should
# be identified in the format @org/team-name. Teams must have
# explicit write access to the repository.
* @climatepolicyradar/software
app/api/api_v1/routers/pipeline_trigger.py @climatepolicyradar/deng
tests/unit/app/core/test_pipeline.py @climatepolicyradar/deng
tests/non_search/app/test_pipeline_trigger.py @climatepolicyradar/deng
app/core/ingestion/ @climatepolicyradar/deng
tests/search/search_fixtures/vespa_test_schema/ @climatepolicyradar/deng
app/api/api_v1/routers/search.py @climatepolicyradar/tech-devs
tests/search/ @climatepolicyradar/tech-devs
app/api/api_v1/schemas/ @climatepolicyradar/tech-devs
tests/unit/app/schemas/ @climatepolicyradar/tech-devs
app/api/api_v1/schemas/search.py @climatepolicyradar/deng