-
Notifications
You must be signed in to change notification settings - Fork 453
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
Easily tell git to ignore built assets #9089
Conversation
Going to have @KorvinSzanto give the thumbs up on this one. |
a569058
to
fabf2c4
Compare
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.
Overall this looks good to merge to me. We should make sure we document this somehow somewhere so that we know where and when to add to the skippable paths.
What about 9a1bad5 ? |
I've had an offline discussion with @KorvinSzanto about calling automatically git-skip when building assets for development, and calling git-unskip when building assets for production. |
Updated with 8d83e39 |
When writing the source javascript/css assets, we often need to build the compiled assets.
When we commit the changes, we may want to commit only the changed source files, not the compiled files.
This is a bit of a mess at the moment.
What about adding an easy way to tell git to ignore the compiled assets?
This pull request:
npm
commands:npm run-script git-skip
tells git to ignore the compiled assetsnpm run-script git-unskip
tells git to consider the compiled assetsgit-skip
when building the assets for development (egnpm run-script dev
)git-unskip
when building the assets for production (egnpm run-script prod
)