-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Put it into the git ignore #79
Comments
we should check, if its not easier with the package-lock 'cause |
I talked shit. It has a proper reason to exist on github |
We should check if its possible to use the yarn.lock inside the github actions |
@oglimmer you've got most experince with gh actions and this stuff |
its completly possible. its just a question, if its required after a year of development.. |
and since the actions've used npm since they exist, I don't get why you used yarn the whole time ;) |
Because @Mickhat asked me to |
aha (oder auf Deutsch: immer schön die Schuld auf andere schieben ;)) |
ja ok |
npm usually gets installed when installing NodeJS. (So why install & switch to yarn?) |
habbit i guess |
Originally posted by @Barsch2006 in #78 (comment)
The text was updated successfully, but these errors were encountered: