generated from t3-oss/create-t3-turbo
-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- [x] Runs formatting on staged files during commit (formatting result will be included in the commit) I'm still not 100% about running lint-staged long term. My main issue is that the hook is terminated if the process running git is killed. The result is that as a dev you're forced to whatever interface for git you're using open during lint-staged or the commit will be arborted. (e.g. if you commit from a pane in your terminal and close it too early the commit won't go through) I'm in favor of merging anyways and reverting if it becomes an issue.
- Loading branch information
Showing
4 changed files
with
246 additions
and
6 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,4 @@ | ||
#!/usr/bin/env sh | ||
. "$(dirname "$0")/_/husky.sh" | ||
|
||
npx lint-staged |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,11 @@ | ||
# Tooling | ||
|
||
## Git hooks | ||
|
||
Packages: | ||
|
||
- Husky: Easier git hook configuration | ||
|
||
- Lint-staged: Run e.g. formatting on staged filed and include result in the commit | ||
|
||
Opt out through the `-n/--no-verify` flag available for most git commands |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.