Empresas
Empleos
  • Sobre nosotros
  • Soluciones
    • Publicación de vacantes
      Publica tu vacante y recibe candidatos calificados en 48h.
    • Evaluación de candidatos
      500+ pruebas técnicas y psicológicas, más anti-fraude.
    • Headhunting
      Búsqueda ejecutiva a la medida de principio a fin.
    • Nómina + EOR
      Dispersión de nómina y EOR en más de 15 países de LATAM.
  • Precios
  • Empleos

0

464
Vistas
Husky 5 .huskey gitignore

10 days ago, Husky 5 was released https://dev.to/typicode/what-s-new-in-husky-5-32g5

after migrating to it (https://typicode.github.io/husky/#/)

I've noticed that there is a new .husky dir in the project.

by default it contains the following:

.huskey
   -> .gitignore
   -> /_

the .gitignore file is simply ignoring the _ dir

_

and inside the /_ dir there is a huskey.sh file which is obviously meant to be ignored.

in the documentation - you add hook by:

npx husky add .husky/pre-commit "npm test"

which will create a pre-commit file inside the .husky dir.

Should I commit that dir with the pre-commit file? not sure about that and can't find that in documentation.

over 4 years ago · Santiago Trujillo
1 Respuestas
Responde la pregunta

0

If you want those hooks to be standard for your repo then yes you will need to commit them. For example, if you have a commit-msg hook to lint commit messages and you want other developers cloning your repo to adhere to those lint rules then the commit-msg file is the way to enforce that.

over 4 years ago · Santiago Trujillo Denunciar
Responde la pregunta
Encuentra empleos remotos

¡Descubre la nueva forma de encontrar empleo!

Top de empleos
Top categorías de empleo
Empresas
Publicar vacante Precios Comercial
Legal
Términos y condiciones Política de privacidad
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Recomiéndame algunas ofertas
Necesito ayuda