(datafusion) branch main updated: ci: Add datafusion/sql as a folder to trigger extended tests for on changes (#21255)

[gi...@apache.org]

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

github-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 2c08ddb4fe ci: Add datafusion/sql as a folder to trigger extended tests for on changes (#21255)
2c08ddb4fe is described below

commit 2c08ddb4fe1e056d23baeab22855f4674904b019
Author: Matt Butrovich <mb...@users.noreply.github.com>
AuthorDate: Mon Mar 30 14:24:28 2026 -0400

    ci: Add datafusion/sql as a folder to trigger extended tests for on changes (#21255)
    
    ## 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.
    -->
    
    - N/A.
    
    ## Rationale for this change
    
    <!--
    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.
    -->
    
    #21126 merged a change that broke the extended tests because its changes
    were scoped to a folder that isn't watched for extended tests on PRs. We
    should watch this folder for changes as well.
    
    ## 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.
    -->
    
    - Watch `datafusion/sql` changes on PRs to trigger extended CI tests as
    well.
    
    ## 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)?
    -->
    
    - Existing CI.
    
    ## 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.
    -->
    
    - No.
---
 .github/workflows/extended.yml | 1 +
 1 file changed, 1 insertion(+)

diff --git a/.github/workflows/extended.yml b/.github/workflows/extended.yml
index 42def10df6..04a0c346f0 100644
--- a/.github/workflows/extended.yml
+++ b/.github/workflows/extended.yml
@@ -44,6 +44,7 @@ on:
       - 'datafusion/physical*/**/*.rs'
       - 'datafusion/expr*/**/*.rs'
       - 'datafusion/optimizer/**/*.rs'
+      - 'datafusion/sql/**/*.rs'
       - 'datafusion-testing'
   workflow_dispatch:
     inputs:


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