rusackas opened a new pull request, #40722:
URL: https://github.com/apache/superset/pull/40722

   ### SUMMARY
   
   `pre-commit`, the Python **unit tests**, and the Postgres **integration 
tests**
   each fan out across Python **3.10 / 3.11 / 3.12** (`previous` / `current` /
   `next`) on *every* PR push. pre-commit (lint/format/mypy) results almost 
never
   differ across patch versions, and the test suites rarely do — so running all
   three per PR roughly triples the runner cost of these jobs for little added
   signal.
   
   This runs **only `current` (3.11) on `pull_request`** events and keeps the
   **full 3-version spread on push** (master/release) and the nightly schedule, 
so
   cross-version regressions are still caught before/at merge. It uses the same
   event-conditional matrix idiom already in the repo for `app_root` in the E2E
   workflow:
   
   ```yaml
   python-version: ${{ github.event_name == 'pull_request'
     && fromJSON('["current"]')
     || fromJSON('["current", "previous", "next"]') }}
   ```
   
   **Per-PR job reduction:** pre-commit 3→1, unit-tests 3→1, integration
   `test-postgres` 3→1 (the mysql/sqlite integration jobs aren't 
version-matrixed).
   
   > **Branch protection note:** if any per-version job is a *required* status
   > check (e.g. `unit-tests (previous)`), update branch protection to require 
the
   > current-only job instead — the other versions no longer run on PRs and 
their
   > checks would otherwise never report.
   
   ### TESTING INSTRUCTIONS
   
   - On this PR: confirm pre-commit / unit-tests / integration `test-postgres` 
each
     run a **single** Python 3.11 job.
   - On push to master: confirm all three versions run.
   
   ### ADDITIONAL INFORMATION
   
   - [ ] Has associated issue:
   - [ ] Changes UI
   - [ ] Includes DB Migration
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API
   
   🤖 Generated with [Claude Code](https://claude.com/claude-code)


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