Skip to content

fix: lint through hatch - #540

Open
flying-sheep wants to merge 5 commits into
mainfrom
hatch-lint
Open

fix: lint through hatch#540
flying-sheep wants to merge 5 commits into
mainfrom
hatch-lint

Conversation

@flying-sheep

Copy link
Copy Markdown
Member

TODO: check what hatch fmt --check does with the missing scripts.

Fixes #539

@github-actions

Copy link
Copy Markdown

A PR has been generated to the instance repo: scverse/cookiecutter-scverse-instance#304

Checks Status Documentation Preview

You can check out the PR to preview your changes in an instance of the cookiecutter template.
It will be kept in sync with this PR automatically.

Comment on lines -56 to +57
prek run --verbose --color=always --show-diff-on-failure --all-files
hatch check fmt --fix -- --verbose --color=always --show-diff-on-failure
hatch check code --fix -- --verbose --color=always --show-diff-on-failure
hatch check types -- --color=always

@flying-sheep flying-sheep Jul 24, 2026

Copy link
Copy Markdown
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

this should probably be reverted except for the “actually typecheck in CI” part

@flying-sheep

Copy link
Copy Markdown
Member Author

@grst @Zethson please take a look

I missed in #530 that this will create a .venv in the repo for type checking – nasty! that’ll confuse users to no end!

@Zethson Zethson left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks for the .venv catch!

I love the added groups & the clarification around where to add type stubs. We could already add the pandas one maybe as an example?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

add linting as hatch command

2 participants