-
-
Notifications
You must be signed in to change notification settings - Fork 31
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
Use of pre-commit #142
Comments
This turns CI to red when pre-commit is not configured for example for Would it be possible to turn it on only on
|
Oh bummer, I thought it would just not run if the file wasn't there. Sure, I'll update to scope it to those two repos. |
Done! |
For those with access, the settings are at: https://github.com/organizations/jupyterlab/settings/installations/24508674 |
Is there a way to re-run the checks? Looks like it fails on the latest commit on
Not sure if it's a real failure or just need to be kicked. |
It seems like the |
I removed it from JupyterLab as well, because we don't have access to What could be done instead is to use the official mirrors for prettier and eslint. Since there is isn't an official mirror for
That would involve trying to de-conflict what is currently part of the top level |
Ha, another, less-hacky idea is to skip all of the local checks on |
@blink1073 could we consider this as resolved? |
Sounds good |
Description
I added the https://pre-commit.ci/ GitHub App to the org. By default this means that any repo with a
.pre-commit-config.yaml
file will get a weekly PR to update the versions used. This will help us keep them up to date easier.cf jupyterlab/jupyterlab#12272
The text was updated successfully, but these errors were encountered: