This is an automated email from the ASF dual-hosted git repository.

kevinjqliu pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/iceberg-python.git


The following commit(s) were added to refs/heads/main by this push:
     new 07e57917b ci: enable ASF Copilot code review (#3740)
07e57917b is described below

commit 07e57917bbde65025cfd16de6c8be585ca39c7f3
Author: Kevin Liu <[email protected]>
AuthorDate: Sun Aug 2 15:08:48 2026 -0400

    ci: enable ASF Copilot code review (#3740)
    
    <!--
    Thanks for opening a pull request!
    -->
    
    <!-- In the case this PR will resolve an issue, please replace
    ${GITHUB_ISSUE_ID} below with the actual Github issue id. -->
    <!-- Closes #${GITHUB_ISSUE_ID} -->
    
    # Rationale for this change
    Inspired by https://github.com/apache/iceberg-cpp/pull/833
    
    This will enable github to automatically request copilot review on PRs
    where the author has access to copilot
    
    ## Are these changes tested?
    
    ## Are there any user-facing changes?
    
    <!-- In the case of user-facing changes, please add the changelog label.
    -->
---
 .asf.yaml                       |  4 ++++
 .github/copilot-instructions.md | 21 +++++++++++++++++++++
 2 files changed, 25 insertions(+)

diff --git a/.asf.yaml b/.asf.yaml
index 32050ad48..fc475098e 100644
--- a/.asf.yaml
+++ b/.asf.yaml
@@ -55,6 +55,10 @@ github:
     - rambleraptor
   ghp_branch: gh-pages
   ghp_path: /
+  copilot_code_review:
+    enabled: true
+    review_drafts: false
+    review_on_push: false
 
 notifications:
     commits:      [email protected]
diff --git a/.github/copilot-instructions.md b/.github/copilot-instructions.md
new file mode 100644
index 000000000..e4a8ef026
--- /dev/null
+++ b/.github/copilot-instructions.md
@@ -0,0 +1,21 @@
+# Instructions
+
+## Code review
+
+You are a pragmatic senior developer. When reviewing pull requests,
+follow these rules to avoid noise and redundancy:
+
+- Be concise: Keep comments brief and to the point. Avoid
+  conversational filler or praising the code unless it's exceptional.
+- High-impact only: Focus on logic errors, security vulnerabilities,
+  performance bottlenecks, and breaking changes.
+- Skip the Obvious: Do not describe what the code is doing. Assume the
+  reader understands the code.
+- Ignore trivialities: Do not comment on minor style issues or things
+  that an automated linter should catch.
+- Single comment per issue: If the same pattern occurs multiple times,
+  mention it once and suggest a global fix instead of commenting on
+  every line.
+- First-time contributors: For users new to this repository,
+  explicitly instruct them to "Please check and address all review
+  comments in this PR."

Reply via email to