-
Notifications
You must be signed in to change notification settings - Fork 14.2k
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
fix(ci): lint issue on update-monorepo-lockfiles.yml #26920
Conversation
@dpgaspar All other workflow files have an empty line at the end. The formatter also adds an empty line automatically. |
It looks like committed files don't have that line. LGTM. |
Ugh... not sure how this snuck through, but this shouldn't have been mergeable in the first place, right? |
Do we not re-run |
Oh @rusackas it's because of this -> https://github.com/apache/superset/blob/master/.github/workflows/superset-python-misc.yml#L10-L13, maybe we should run pre-commit across the board, it's pretty cheap anyways, and many checks are not python-specific anymore |
#26920 caught an issue that should have been picked up by pre-commit (by the user), but then re-caught by CI, preventing the merge. The reason is was not caught was that the CI check is part of a group of python misc checks that trigger only where the python package's folder has changed. In reality, the python utility pre-commit we use here is used for much more than just Python files, so we should run it across the repo. Here I simply factored out the check into its own GitHub Action that triggers for every single CI run.
Preventing this here -> #26942 |
SUMMARY
Fixes lint issue on
update-monorepo-lockfiles.yml
, impacts open PRsBEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
TESTING INSTRUCTIONS
ADDITIONAL INFORMATION