Skip to content

Test "determine-changes" step for formatter only change" #16799

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed

Conversation

MichaReiser
Copy link
Member

@MichaReiser MichaReiser commented Mar 17, 2025

GitHub actions should skip the ruff linter ecosystem check

@MichaReiser MichaReiser added the ci Related to internal CI tooling label Mar 17, 2025
@MichaReiser MichaReiser force-pushed the micha/formatter-change branch from 30466a5 to 36b389c Compare March 17, 2025 11:18
@MichaReiser MichaReiser added the do-not-merge Do not merge this pull request label Mar 17, 2025
@MichaReiser MichaReiser force-pushed the micha/formatter-change branch from 36b389c to 1d3f890 Compare March 17, 2025 11:24
Copy link
Contributor

github-actions bot commented Mar 17, 2025

ruff-ecosystem results

Formatter (stable)

✅ ecosystem check detected no format changes.

Formatter (preview)

✅ ecosystem check detected no format changes.

@MichaReiser MichaReiser force-pushed the micha/formatter-change branch from 1d3f890 to 51c3f60 Compare March 17, 2025 11:32
MichaReiser added a commit that referenced this pull request Mar 17, 2025
## Summary

Use bash and `git diff` to determine which steps need to run. 

We previously used the `changed-files` github actions but using `git`
directly seems simple enough.

All credit for the bash magic goes to @zanieb and @geofft. All I did was
replace the paths arguments.


## Test Plan

* [Linter only change](#16800):
See how the fuzzer and formatter steps, and the linter ecosystem checks
are skipped
* [Formatter only change](#16799):
See how the fuzzer and linter ecosystem checks are skipped
@MichaReiser MichaReiser deleted the micha/formatter-change branch May 3, 2025 17:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
ci Related to internal CI tooling do-not-merge Do not merge this pull request
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant