CODEOWNERS: just use the kpt-reviewers group everywhere (#3621)

We don't need the complex rules now that we have one group.
kptdev · Oct 14, 2022 · 9dd3319 · 9dd3319
1 parent 212b668
commit 9dd3319
Showing 1 changed file with 2 additions and 12 deletions.
diff --git a/CODEOWNERS b/CODEOWNERS
@@ -1,15 +1,5 @@
 # Generally we are following a permissive policy of code ownership
 # We use the @GoogleContainerTools/kpt-reviewers group so that we can assign a single person to each PR.
 
-# Docs
-/site @GoogleContainerTools/kpt-reviewers
-# These packages are referenced in docs.
-/package-examples/nginx/ @GoogleContainerTools/kpt-reviewers
-/package-examples/wordpress/ @GoogleContainerTools/kpt-reviewers
-
-# Schemas changes additional scrutiny.
-/pkg/api @GoogleContainerTools/kpt-reviewers
-
-# These tests enforce the behavior for fn
-kpt/e2e/testdata/fn-render @GoogleContainerTools/kpt-reviewers
-kpt/e2e/testdata/fn-eval @GoogleContainerTools/kpt-reviewers
+# Default
+/ @GoogleContainerTools/kpt-reviewers