-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
github actions black run suddenly failing #3538
Comments
I locally upgraded to black 23.1.0 (latest version) and the changes it wants look quite the same as what I see on github actions. So I suspect that To actually see the version it really installed on github actions, it would be useful if black told its version before it shows the diff. |
work around the current github actions issue by just using the latest version: psf/black#3538
A temporary workaround might be to just upgrade / pin to the current version ( |
Quite confusingly, the GH Action's version is independent from the version of Black that is used to format the code. #3282 is tracking the fix for this issue. See https://black.readthedocs.io/en/stable/integrations/github_actions.html for how to format the version of Black used by the action. |
@JelleZijlstra the issue you linked is about Jupyter notebooks. The docs link was helpful, thanks! https://github.com/borgbackup/borg/pull/7316/files |
Sorry, I meant #3382. |
Describe the bug
We suddenly have black fail on a PR that has no related changes.
After merging the PR, black is now also failing on master branch.
https://github.com/borgbackup/borg/actions/runs/4063411463/jobs/6995614199
https://github.com/borgbackup/borg/blob/master/.github/workflows/black.yaml
We pinned black to 22.6.0 there, log says:
We also use that locally via our
requirements.d/codestyle.txt
.If I run black 22.6.0 locally, it says everything is fine and it doesn't want to reformat anything.
Expected behavior
Should behave the same way locally as on github actions if using same black version.
Environment
Additional context
It worked fine until about today (2023-02-01).
Here is a black run of yesterday:
https://github.com/borgbackup/borg/actions/runs/4059816119/jobs/6988280083
Master branch, single-line changeset, no complaints.
The text was updated successfully, but these errors were encountered: