(datafusion) branch main updated: chore: extend pre commit instructions for AI agents (#23313)

[gi...@apache.org]

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

github-merge-queue[bot] pushed a commit to branch main
in repository https://gitbox.apache.org/repos/asf/datafusion.git


The following commit(s) were added to refs/heads/main by this push:
     new 0fcaef3e8a chore: extend pre commit instructions for AI agents (#23313)
0fcaef3e8a is described below

commit 0fcaef3e8a29fd174b6e3f22ee936a7283b599a4
Author: Oleks V <co...@users.noreply.github.com>
AuthorDate: Fri Jul 3 16:07:24 2026 -0700

    chore: extend pre commit instructions for AI agents (#23313)
    
    ## Which issue does this PR close?
    
    <!--
    We generally require a GitHub issue to be filed for all bug fixes and
    enhancements and this helps us generate change logs for our releases.
    You can link an issue to this PR using the GitHub syntax. For example
    `Closes #123` indicates that this PR will close issue #123.
    -->
    
    - Closes #22455 .
    
    ## Rationale for this change
    
    Extend pre commit instructions for AI agents to involve contributor
    machine to find issues before being committed. Each commit triggers a CI
    which in its turn asks ASF Infra for their precious resources and if we
    can find and fix as early as possible, much before utilizing ASF
    resources, would be amazing
    
    <!--
    Why are you proposing this change? If this is already explained clearly
    in the issue then this section is not needed.
    Explaining clearly why changes are proposed helps reviewers understand
    your changes and offer better suggestions for fixes.
    -->
    
    ## What changes are included in this PR?
    
    <!--
    There is no need to duplicate the description in the issue here but it
    is sometimes worth providing a summary of the individual changes in this
    PR.
    -->
    
    ## Are these changes tested?
    
    <!--
    We typically require tests for all PRs in order to:
    1. Prevent the code from being accidentally broken by subsequent changes
    2. Serve as another way to document the expected behavior of the code
    
    If tests are not included in your PR, please explain why (for example,
    are they covered by existing tests)?
    -->
    
    ## Are there any user-facing changes?
    
    <!--
    If there are user-facing changes then we may require documentation to be
    updated before approving the PR.
    -->
    
    <!--
    If there are any breaking changes to public APIs, please add the `api
    change` label.
    -->
---
 AGENTS.md | 16 ++++++++++++++--
 1 file changed, 14 insertions(+), 2 deletions(-)

diff --git a/AGENTS.md b/AGENTS.md
index 13515d9e6c..1b61183e0b 100644
--- a/AGENTS.md
+++ b/AGENTS.md
@@ -37,8 +37,20 @@ When creating a PR, you MUST follow the [PR template](.github/pull_request_templ
 
 ## Testing
 
-See the [Testing Quick Start](docs/source/contributor-guide/testing.md#testing-quick-start)
-for the recommended pre-PR test commands.
+If documentation files changed then run 
+```bash
+./ci/scripts/doc_prettier_check.sh --write --allow-dirty
+```
+
+Otherwise, run extended tests
+```bash
+RUST_BACKTRACE=1 cargo test --profile ci \
+    --exclude datafusion-examples --exclude datafusion-benchmarks --exclude datafusion-cli \
+    --workspace --lib --tests --bins \
+    --features avro,json,backtrace,extended_tests,recursive_protection,parquet_encryption
+```
+
+For modified code identify local benchmarks(if any) and run them against `main`. See [Benchmarks](benchmarks/README.md).
 
 ## Agent Skills
 


---------------------------------------------------------------------
To unsubscribe, e-mail: commits-unsubscribe@datafusion.apache.org
For additional commands, e-mail: commits-help@datafusion.apache.org