diff --git a/.github/scripts/automerge.sh b/.github/scripts/automerge.sh
new file mode 100644
index 0000000000000..0e2c79b9a2f47
--- /dev/null
+++ b/.github/scripts/automerge.sh
@@ -0,0 +1,18 @@
+TOPIC_BRANCH=$1
+do_conf() {
+	# Define the filename
+	FILENAME="merge.conf"
+
+# Create the file with the specified content
+cat <<EOF > "$FILENAME"
+baseline git@github.com:qualcomm-linux/kernel.git       qcom-next 
+$TOPIC_BRANCH git@github.com:qualcomm-linux/kernel-topics.git       $TOPIC_BRANCH
+EOF
+
+	echo "File '$FILENAME' created successfully."
+}
+
+do_conf
+
+cd kernel
+../automerge/ci-merge -f ../merge.conf -t head -n
diff --git a/.github/workflows/pr.yml b/.github/workflows/pr.yml
new file mode 100644
index 0000000000000..8d2ff44887761
--- /dev/null
+++ b/.github/workflows/pr.yml
@@ -0,0 +1,29 @@
+name: pre_merge
+on:
+  pull_request:
+  workflow_dispatch:
+  
+jobs:
+  sync:
+    runs-on: self-hosted
+    steps:
+      - name: Create merge configuration
+        run: |
+          TOPIC_BRANCH=${{ github.base_ref }}
+          cat <<EOF > merge.conf
+          baseline git@github.com:qualcomm-linux/kernel.git qcom-next
+          $TOPIC_BRANCH git@github.com:quic-viskuma/kernel-topics.git $TOPIC_BRANCH
+          EOF
+          echo "File 'merge.conf' created successfully."
+
+      - name: Run auto merge
+        run: |
+          cd kernel
+          ../automerge/ci-merge -f ../merge.conf -t head -n
+
+      - name: Fetch the PR 
+        run: |
+          cd kernel
+          git fetch ${{ github.base_ref }} pull/${{ github.event.pull_request.number }}/head:pr-${{ github.event.pull_request.number }}
+          git checkout pr-${{ github.event.pull_request.number }}
+
diff --git a/README b/README
deleted file mode 100644
index fd903645e6de0..0000000000000
--- a/README
+++ /dev/null
@@ -1,18 +0,0 @@
-Linux kernel
-============
-
-There are several guides for kernel developers and users. These guides can
-be rendered in a number of formats, like HTML and PDF. Please read
-Documentation/admin-guide/README.rst first.
-
-In order to build the documentation, use ``make htmldocs`` or
-``make pdfdocs``.  The formatted documentation can also be read online at:
-
-    https://www.kernel.org/doc/html/latest/
-
-There are various text files in the Documentation/ subdirectory,
-several of them using the reStructuredText markup notation.
-
-Please read the Documentation/process/changes.rst file, as it contains the
-requirements for building and running the kernel, and information about
-the problems which may result by upgrading your kernel.