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

   ### SUMMARY
   Spike/experiment, not proposing to merge yet.
   
   [prek](https://github.com/j178/prek) is a Rust reimplementation of 
`pre-commit` that reads the same `.pre-commit-config.yaml` unmodified, shares 
toolchains/environments across hooks instead of building a fresh venv per repo, 
and claims (and, per CPython/FastAPI/Apache Airflow's adoption, has apparently 
delivered) substantially faster cold-start and warm-run CI times.
   
   This PR swaps only the binary this workflow invokes — same changed-files 
diffing logic, same `SKIP` handling, same fail-closed behavior, just `prek run` 
instead of `pre-commit run`, plus repointing the environment cache from 
`~/.cache/pre-commit` to `~/.cache/prek`.
   
   **Explicitly out of scope here:** anything contributor-facing. `pre-commit 
install` / `pre-commit run` locally, `requirements/development.txt`, and the 
contributing docs are all untouched. If this spike pans out, adopting prek 
locally (optionally via its `pre-commit`-shim install mode, so the command 
contributors already type keeps working) would be a separate, later decision.
   
   ### BEFORE/AFTER
   Before: this job runs `pre-commit run [--all-files|--files ...]`, caching 
`~/.cache/pre-commit`.
   After: this job runs `prek run [--all-files|--files ...]` against the same 
config, caching `~/.cache/prek`.
   
   ### TESTING INSTRUCTIONS
   Watch this PR's own `pre-commit checks` job — it's exercising the change on 
itself. Ran `prek validate-config`, `prek list`, and targeted `prek run` 
invocations locally first (all 23 hooks in `.pre-commit-config.yaml` resolve; 
spot-checked `ruff`/`ruff-format`/`zizmor` execution and `SKIP` env var 
behavior) before pushing.
   
   ### ADDITIONAL INFORMATION
   - [ ] Has associated issue:
   - [ ] Required feature flags:
   - [ ] Changes UI
   - [ ] Includes DB Migration (follow approval process in 
[SIP-59](https://github.com/apache/superset/issues/13351))
     - [ ] Migration is atomic, supports rollback & is backwards-compatible
     - [ ] Confirm DB migration upgrade and downgrade tested
     - [ ] Runtime estimates and downtime expectations provided
   - [ ] Introduces new feature or API
   - [ ] Removes existing feature or API


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