-
Notifications
You must be signed in to change notification settings - Fork 18
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
Add note to development setup docs about committing built files #157
Conversation
Perfect, thanks a lot @ChristophWurst – that is a sentence we can also use in other apps where this is a requirement. :) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks ✌️
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Unnecessary but could be nice to have: should the message include the command to run, npm run build
in this case?
90086a1
to
6f49ab1
Compare
@gary-kim good point – added that. :) Ready to 🚢! |
DCO says no. Mind squashing? |
Co-Authored-By: Christoph Wurst <[email protected]> Signed-off-by: Jan-Christoph Borchardt <[email protected]>
6f49ab1
to
8992a03
Compare
Squashed into a signed commit, should run through now :) |
Added this cause I was unsure whether the built files have to be committed or not. So here’s a note for clarification. :)
As per your comment @ChristophWurst #156 (review)
Does this sound good?