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