From 807fa52814ce455423911e186854e47f58b8fbeb Mon Sep 17 00:00:00 2001
From: gerinc <100672567+gorkem-pointr@users.noreply.github.com>
Date: Wed, 29 Jan 2025 17:18:55 +0300
Subject: [PATCH] Add CODEOWNERS

---
 .github/CODEOWNERS | 29 +++++++++++++++++++++++++++++
 1 file changed, 29 insertions(+)
 create mode 100644 .github/CODEOWNERS

diff --git a/.github/CODEOWNERS b/.github/CODEOWNERS
new file mode 100644
index 000000000..645d8c9e8
--- /dev/null
+++ b/.github/CODEOWNERS
@@ -0,0 +1,29 @@
+# CODEOWNERS
+#
+# This file is used to define individuals or teams that are responsible for code
+# in this repository. Each line in this file specifies a path and the GitHub
+# username(s) or team(s) that are responsible for that path.
+#
+# Syntax:
+# - Lines starting with '#' are comments.
+# - Each line specifies a file pattern followed by one or more owners.
+# - File patterns are relative to the repository root.
+# - Owners can be individual GitHub usernames or team names (in the form of @org/team-name).
+# - Use teams where possible, as they are easier to maintain.
+# - Each owner must be separated by one or more spaces.
+# - Blank lines are ignored.
+#
+# Example:
+# *                @username        # Owner of the entire repository
+# /docs/*          @docsteam        # Team responsible for the /docs directory
+# /src/**/*.js     @frontendteam    # Team responsible for all JavaScript files in /src
+#
+# The CODEOWNERS file helps ensure that code reviews are assigned to the right people,
+# making it easier to maintain code quality and streamline the review process.
+#
+# For more details, refer to the GitHub documentation on CODEOWNERS:
+# https://docs.github.com/en/github/creating-cloning-and-archiving-repositories/about-code-owners
+
+* @pointrlabs/rd
+
+.github/* @pointrlabs/devops