|
1 | | -# This is a comment. |
2 | | -# Each line is a file pattern followed by one or more owners. |
3 | | - |
4 | | -# These owners will be the default owners for everything in |
5 | | -# the repo. Unless a later match takes precedence, |
6 | | -# These users will be requested for |
7 | | -# review when someone opens a pull request. |
8 | | -* @kgrhartlage @ignatiusreza |
9 | | - |
10 | | -# Order is important; the last matching pattern takes the most |
11 | | -# precedence. When someone opens a pull request that only |
12 | | -# modifies JS files, only @js-owner and not the global |
13 | | -# owner(s) will be requested for a review. |
14 | | -# *.js @js-owner |
15 | | - |
16 | | -# You can also use email addresses if you prefer. They'll be |
17 | | -# used to look up users just like we do for commit author |
18 | | -# emails. |
19 | | - |
20 | | - |
21 | | -# In this example, @doctocat owns any files in the build/logs |
22 | | -# directory at the root of the repository and any of its |
23 | | -# subdirectories. |
24 | | -# /build/logs/ @doctocat |
25 | | - |
26 | | -# The `docs/*` pattern will match files like |
27 | | -# `docs/getting-started.md` but not further nested files like |
28 | | -# `docs/build-app/troubleshooting.md`. |
29 | | - |
30 | | - |
31 | | -# In this example, @octocat owns any file in an apps directory |
32 | | -# anywhere in your repository. |
33 | | -# apps/ @octocat |
34 | | - |
35 | | -# In this example, @doctocat owns any file in the `/docs` |
36 | | -# directory in the root of your repository. |
37 | | -# /docs/ @doctocat |
| 1 | +@laboperator-gmbh/application |
0 commit comments