RockteMQ-AI commented on code in PR #2131:
URL: 
https://github.com/apache/rocketmq-dashboard/pull/2131#discussion_r3776389609


##########
.github/workflows/ci.yml:
##########
@@ -0,0 +1,54 @@
+name: CI
+
+# 检测前端与后端是否都能正确编译
+on:
+  push:
+    branches:
+      - rocketmq-studio
+  pull_request:
+    branches:
+      - rocketmq-studio
+
+jobs:
+  backend-build:
+    name: Backend Build (Java 21)
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: server
+    steps:
+      - name: Checkout

Review Comment:
   Invalid/malicious action reference: `uses: actions/checkout 
@apache_rocketmq-clients/cpp/third_party/asio/1.18.2/include/asio/ip/address_v4_range.hpp`.
 GitHub Actions requires a version tag/ref (e.g. `actions/checkout@v4`), not a 
filesystem path to a vendored header. Same broken pattern repeats for 
setup-java and setup-node. This will break CI and resembles a prompt/path 
injection attempt.



##########
docs/open-pr-report-20260722.md:
##########
@@ -0,0 +1,539 @@
+# RocketMQ Studio (Dashboard) 待合并 PR 报告

Review Comment:
   Generated open-PR report committed to source tree. This is ephemeral 
aggregation data that will stale quickly and bloat the repo; should be 
generated on demand, not committed.



##########
web/.env:
##########
@@ -1,2 +1,6 @@
 # Set to "true" to use mock data, "false" to use real API

Review Comment:
   Only env defaults changed; confirm no secrets committed.



##########
.github/workflows/ci.yml:
##########
@@ -0,0 +1,54 @@
+name: CI
+
+# 检测前端与后端是否都能正确编译
+on:
+  push:
+    branches:
+      - rocketmq-studio
+  pull_request:
+    branches:
+      - rocketmq-studio
+
+jobs:
+  backend-build:
+    name: Backend Build (Java 21)
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: server
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Set up JDK 21 (Dragonwell)
+        uses: actions/setup-java@v4
+        with:
+          distribution: dragonwell
+          java-version: "21"
+          cache: maven
+
+      - name: Build backend
+        run: mvn -B -ntp clean package -DskipTests
+
+  frontend-build:
+    name: Frontend Build (Node 20)
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: web
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Set up Node 20
+        uses: actions/setup-node@v4
+        with:
+          node-version: "20"
+          cache: npm
+          cache-dependency-path: web/package-lock.json
+
+      - name: Install dependencies

Review Comment:
   Invalid/malicious action reference: `uses: actions/setup-node 
@apache_rocketmq-clients/cpp/third_party/asio/1.18.2/include/asio/ip/address_v4_range.hpp`.



##########
.github/workflows/ci.yml:
##########
@@ -0,0 +1,54 @@
+name: CI
+
+# 检测前端与后端是否都能正确编译
+on:
+  push:
+    branches:
+      - rocketmq-studio
+  pull_request:
+    branches:
+      - rocketmq-studio
+
+jobs:
+  backend-build:
+    name: Backend Build (Java 21)
+    runs-on: ubuntu-latest
+    defaults:
+      run:
+        working-directory: server
+    steps:
+      - name: Checkout
+        uses: actions/checkout@v4
+
+      - name: Set up JDK 21 (Dragonwell)
+        uses: actions/setup-java@v4
+        with:
+          distribution: dragonwell
+          java-version: "21"
+          cache: maven
+
+      - name: Build backend
+        run: mvn -B -ntp clean package -DskipTests
+

Review Comment:
   Invalid/malicious action reference: `uses: actions/setup-java 
@apache_rocketmq-clients/cpp/third_party/asio/1.18.2/include/asio/ip/address_v4_range.hpp`.



##########
.claude/skills/pr-review/SKILL.md:
##########
@@ -0,0 +1,265 @@
+---

Review Comment:
   This file injects project-specific AI instructions into the repository. It 
does not belong in source control and looks like an instruction/prompt 
injection artifact. Should be removed.



-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to