Skip to content

Commit 14a9169

Browse files
committed
Adding CODEOWNERS file. Also linking adding clickable links to the trusted commiters.
1 parent c6801f7 commit 14a9169

File tree

2 files changed

+46
-6
lines changed

2 files changed

+46
-6
lines changed

.github/CODEOWNERS

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

TRUSTED-COMMITTERS.md

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -4,11 +4,11 @@ Trusted committers (TCs) are those members of our working group who have elevate
44

55
## Current Trusted Committers
66

7-
* @lenucksi
8-
* @nyeates
9-
* @gruetter
10-
* @NewMexicoKid
11-
* @cewilliams
7+
* [@lenucksi](https://github.com/lenucksi)
8+
* [@nyeates](https://github.com/nyeates)
9+
* [@gruetter](https://github.com/gruetter)
10+
* [@NewMexicoKid](https://github.com/NewMexicoKid)
11+
* [@cewilliams](https://github.com/cewilliams)
1212

1313
## Process for Adding new Trusted Committers
1414

@@ -30,6 +30,6 @@ We follow this process (adapted from [here](https://tech.europace.de/voting-in-n
3030
* New TC is added to the #innersource-patterns-tcs channel
3131
* New TC is praised in the [#innersource-patterns](https://app.slack.com/client/T04PXKRM0/C2EFRTS6A) channel.
3232

33-
3433
## Admins
34+
3535
A handful of individuals are currently the technical GitHub Admins for this repository. This includes most members of the InnerSource Commons' #tech-infra team and members of the [InnerSource Commons GitHub Organization](https://github.com/innersourcecommons). However, please channel working group-specific requests through the trusted committers.

0 commit comments

Comments
 (0)