Run linter on commit instead of push

[Amxx]

Doing that on push means we run lint when pushing tags, deleting remove banches, ... things that really don't need to run the linter.

Using husky and staged-lint to keep the project cleaner, (and stop reinventing the weel)

[changeset-bot]

⚠️ No Changeset found

Latest commit: f5bbf61

Merging this PR will not cause a version bump for any packages. If these changes should not result in a new version, you're good to go. If these changes should result in a version bump, you need to add a changeset.

This PR includes no changesets

When changesets are added to this PR, you'll see the packages that this PR includes changesets for and the associated semver types

Click here to learn what changesets are, and how to add one.

Click here if you're a maintainer who wants to add a changeset to this PR

[Amxx]

@frangio I'm sure you'll have interresting feedback on this

[frangio]

I have my opinions but I think it's up to you who will deal with this regularly. Technically this change seems fine. You could look into lint-staged if you wanted something that does the filtering out of the box.

[socket-security]

New and removed dependencies detected. Learn more about Socket for GitHub ↗︎

Package	New capabilities	Transitives	Size	Publisher
npm/[email protected]	None	0	4.04 kB	typicode
npm/[email protected]	Transitive: environment, filesystem, shell	+46	1.98 MB	okonet
npm/[email protected]	None	+5	240 kB	doowb

🚮 Removed packages: npm/[email protected], pypi/[email protected], pypi/[email protected]

View full report↗︎

[ernestognw]

Using husky and staged-lint to keep the project cleaner, (and stop reinventing the weel)

I agree but I think it should be a balance. These two dependencies are fine but we're also extending the surface of maintaining and securing dependencies. We don't enjoy doing that much and is always low priority