Skip to content

Multiple issues with change_detector.py script #44822

Description

@hainenber

Bug description

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.11

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • I have searched Superset docs and Slack and didn't find a solution to my problem.
  • I have searched the GitHub issue tracker and didn't find a similar bug report.
  • I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Activity

  1. rusackas commented on Sep 30, 2026

    @rusackas
    Member

    Both legit! You've already got the right fix in mind for each. Want to open a PR since you're already deep in change_detector.py, or would you rather this be up for grabs for anyone?

  2. hainenber commented on Sep 30, 2026

    @hainenber
    ContributorAuthor

    It's up for grabs for everyone. Good first issues even :D

  3. tarunchaudharydev commented on Sep 30, 2026

    @tarunchaudharydev

    I'd like to work on this issue. I'll investigate the current change_detector.py behavior for multi-commit push events and submit a PR with tests.

  4. Roshan1299 commented on Sep 30, 2026

    @Roshan1299

    Hi @hainenber , I'd like to work on this! Can I be assigned?

  5. Adarsh-mk7 commented on Oct 1, 2026

    @Adarsh-mk7

    Hi there! I'd love to take a look at fixing these issues with change_detector.py. Could you please assign this issue to me?

  6. kksingh000 commented on Oct 1, 2026

    @kksingh000
    Contributor

    I'd like to pick up the language-classification half of this (the python/frontend directory-group conflation in change_detector.py's PATTERNS, referenced in the review discussion on PR #44699). The push-range half is already in progress in #44833, so I'll leave that alone.

    Before I start: on current master, codeql-analysis.yml's analyze job still runs the hardcoded ["python", "javascript"] matrix whenever python == 'true' || frontend == 'true' -- the per-language lang_matrix output that would actually consume a more accurate classification only exists on #44699's branch, which isn't merged yet. So fixing PATTERNS to be language-accurate on master today wouldn't change CodeQL's behavior until #44699 lands (or is rebased onto this).

    @hainenber -- is a standalone fix to PATTERNS (making python/frontend classify by file extension/language rather than directory) still useful to land ahead of #44699, or would you rather this be folded into that PR directly once it's further along? Don't want to duplicate work or build something that conflicts with how you're planning to finish #44699.

  7. hainenber commented on Oct 2, 2026

    @hainenber
    ContributorAuthor

    Go ahead with the lang-classify issue, @kksingh000. Please have your PR independent of my linked PR, i.e keep targeting main.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions