Skip to content
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.

Sign up for GitHub

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

Jump to bottom

Remove always failing linter #136

Merged
merged 1 commit into from
Jul 25, 2024
Merged

Remove always failing linter #136

merged 1 commit into from
Jul 25, 2024

Commits on Jul 19, 2024

  1. Remove always failing linter 

    This was introduced in jupyterhub#106,
and has never passed. I don't think we should have a test that is always
expected to fail.

If it should be re-introduced, it should be done in such a way that
whatever changes are needed to make it pass should be part of the PR.

This only reverts the linter, but keeps the rendering test - as that would
help us catch possible jsonnet syntax issues.
    @yuvipanda
    yuvipanda committed Jul 19, 2024
    Configuration menu
    Copy the full SHA
    dc43320 View commit details
    Browse the repository at this point in the history