tree 157acd8dd5fb5ab9df28e7939ba131c1ae077823
parent f0545153d506a7e63e2494d0113695f67f1a260e
author Jarek Potiuk <jarek@potiuk.com> 1598703050 +0200
committer GitHub <noreply@github.com> 1598703050 +0200
gpgsig -----BEGIN PGP SIGNATURE-----
 
 wsBcBAABCAAQBQJfSkXKCRBK7hj4Ov3rIwAAdHIIAI1XCzFGLS/lSBy6mqTZzvSD
 vQeSBU6vjxrzYZ91o/YcjP7jUBdhGqNWb/N5qSqf900rb/C7TXP8JZKT/9myveyn
 cFW4jdlwOjsE5/HmyBXWdRQGyanmuBzbXZ/NpoIqrqG7x2x1sRiITHzcNAMcLh0i
 u35z8zTjh5pNb89XxJEW7IupT/I9bISjP4f10kW4v8+BSe3xLRST4m5QWOm1inr6
 PgdiwRwdxg73n+GKodW2h/wPMNKNYGRE/IN2Fw7IbYxQlLIFSi/wdlEkVWRVLU0R
 8Y1oTqlkz1pQHK0iNreWAdr20RelrMzy18usQQ7VLpYa826NPJMhpmJqnVRRbwA=
 =9Lg1
 -----END PGP SIGNATURE-----
 

Fix pre commit failing on modified ts code (#4)

* The npm release step will not add generated files automaticaly

Previously the release step was adding the generated dist
files to git automatically, which was not a good idea because
pre-commit did not fail in case someone modified the .ts file

Now the pre-commit check for npm will behave like all other
pre-commit checks - if a file will be modified by the check,
the file will not be added and pre-commit check will fail
allowing the author to add the file manually.