-
I'm thinking about the best approach for implementing pipelines based on existing workspaces (such as #27 and #28).
The primary goal is to ensure ease of use, while maintaining minimal code duplica…
-
#
[https://lim-frontend.vercel.app/posts/240303-husky](https://lim-frontend.vercel.app/posts/240303-husky)
-
## Description
When husky installed and in `package.json` `prepare: husky install` script exists np crashes with
```
✖ SyntaxError: Unexpected token '>', "
> kirka@5."... is not valid JSON…
-
### Description
currently in our project we don't have husky if we use husky we can easily formatting the code if before the make the commit by using pre commit
### Screenshots
_No response_
### …
-
https://typicode.github.io/husky/
-
As a developer I want auto check my commit changes (use [Husky](https://typicode.github.io/husky/#/) for that)
AC:
- Define commit message rules
- prevent from committing with prettier warnings
-
Setup husky: https://typicode.github.io/husky/#/
Example: https://github.com/EddieHubCommunity/LinkFree/blob/main/.husky/pre-commit
-
I hope, the changes in the codebase won't be huge, otherwise may be it's not so good idea...
-
Cause I keep on forgetting to clean up imports
-
• gostreamdeck: Settings:Output ColorSpace
• gostreamdeck: Settings:OutFormat
• gostreamdeck: Settings:Src Selection
• gostreamdeck: Settings:Mic Input
• gostreamdeck: Settings:Set Mv Layout
• go…