github-actions[bot] commented on code in PR #62302:
URL: https://github.com/apache/doris/pull/62302#discussion_r3063179837


##########
.github/workflows/opencode-review-comment.yml:
##########
@@ -0,0 +1,75 @@
+name: Code Review Comment Dispatch
+
+on:
+  issue_comment:
+    types: [created]
+
+permissions:
+  actions: write
+  pull-requests: write
+  contents: read
+  issues: write
+
+jobs:
+  resolve-pr:
+    runs-on: ubuntu-latest
+    if: >-
+      github.event.issue.pull_request &&

Review Comment:
   `issue_comment` runs in the base repository context, but this job only 
checks for a `/review` substring before invoking a reusable workflow with 
`secrets: inherit`. That means any outside user who can comment on a public PR 
can trigger a secret-backed run over untrusted head code. Please gate this on 
trusted `author_association` values and refuse fork heads (or avoid inheriting 
sensitive secrets entirely).



##########
.github/workflows/pr-approve-status.yml:
##########
@@ -1,43 +0,0 @@
-# Licensed to the Apache Software Foundation (ASF) under one
-# or more contributor license agreements.  See the NOTICE file
-# distributed with this work for additional information
-# regarding copyright ownership.  The ASF licenses this file
-# to you under the Apache License, Version 2.0 (the
-# "License"); you may not use this file except in compliance
-# with the License.  You may obtain a copy of the License at
-#
-#   http://www.apache.org/licenses/LICENSE-2.0
-#
-# Unless required by applicable law or agreed to in writing,
-# software distributed under the License is distributed on an
-# "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY
-# KIND, either express or implied.  See the License for the
-# specific language governing permissions and limitations
-# under the License.
----
-name: Need_2_Approval

Review Comment:
   Removing this workflow breaks the repository's current `master` protection 
rules: `.asf.yaml:65` still requires the `Need_2_Approval` status, and there is 
no remaining workflow that publishes the same context. After merge, PRs will be 
permanently missing a required check unless the protection config is updated in 
the same change or this status is replaced.



-- 
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]


---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to