Why are so many static tests switched off?

[samwaseda]

pyironFlow/.github/workflows/push-pull.yml

Lines 10 to 27 in b975267

	jobs:
	pyiron:
	uses: pyiron/actions/.github/workflows/push-pull.yml@actions-4.0.10
	secrets: inherit
	with:
	do-commit-updated-env: true
	do-build-docs: false
	do-build-notebooks: true
	do-unit-tests: false
	do-codecov: false
	do-codacy: false
	do-coveralls: false
	do-benchmark-tests: false
	do-pip-check: false
	do-black: false
	do-ruff-check: false
	do-ruff-sort-imports: false
	do-mypy: false

I realized that so many of the static tests are deactivated. Is there a particular reason? @liamhuber

[jan-janssen]

I would assume they need more fixes to pass, but feel free to open a pull request to activate them.

[liamhuber]

Main answer: Jan is spot on, and we can simply start turning these on.

Big caveat: Please be judicious in actually doing this. @juliusmittler has been working on the repo for a while in #136, and has touched a lot of the files. What I strongly want to avoid is causing him a big headache of a merge conflict. So, for instance, turning on the notebook tests is probably fine, but

History: I wanted to get the binder button working again ASAP before some of the recent workshops, so I leveraged the infrastructure but left most of it turned off to get things done and leave an easy path forwards.

Future: @juliusmittler, we should actually get your stuff merged pretty soon here; even if the loop functionality is still just a beta, I want to get everything you've done in and there so what's left will be more targeted changes and we can better co-work without merge conflicts.