No, you don't.
To check if people have done what - committed? That's the only thing they need to do, and they'll stumble upon a roadblock immediately if the typecheck or lint fails.
Committing itself won't be possible... That's why we have automated pre-commit checks that don't depend on people remembering to do them manually.
Very good advices!
They don't have to follow anything except try to commit their changes. Won't be possible even locally if linting or typechecking fail.
Yep, I'd say so too. The moment I read the part about formatting in the CI, I thought to myself: I don't think GitHub Actions are the problem at hand. ๐
Do formatting and linting and such autofix issues automatically as part of pre-commit checks. That way they don't end up as part of the CI.
It's a lot friendlier with friends. ๐ป
Thanks for the script approach idea!
Yeah, https was for downloading it in the first place. My bad, I didn't get my thoughts out in the right order.
I think safer approach is to:
Yeah, I don't need it but I wanna have it. ๐
It's bubbling up. ๐
They're optional if you make them optional. I didn't. You do as you please. ๐