Welcome to Software Development on Codidact!
Will you help us build our independent community of developers helping developers? We're small and trying to grow. We welcome questions about all aspects of software development, from design to code to QA and more. Got questions? Got answers? Got code you'd like someone to review? Please join us.
Post History
One thing to consider if you decide to store the CSS in version control is how to make sure that the CSS is always updated whenever the SASS is updated. (Of course this is true of the more general ...
Answer
#1: Initial revision
One thing to consider if you decide to store the CSS in version control is how to make sure that the CSS is always updated whenever the SASS is updated. (Of course this is true of the more general question, not just about CSS and SASS.) My preferred way to do that is to add a pre-commit hook to the project that runs the build scripts for any built files I'm keeping in version control. The nature of the pre-commit hook will depend on what version control system you're using. If you're using Subversion, for example, you can [add the hook](http://svnbook.red-bean.com/en/1.7/svn.reposadmin.create.html#svn.reposadmin.create.hooks) to the Subversion server; if you're using Git, you *could* just add the hook into your [`.git/hooks` directory](https://git-scm.com/book/en/v2/Customizing-Git-Git-Hooks) manually, but I'd recommend using a tool like [Husky](https://www.npmjs.com/package/husky) so that anyone else who works on your project will get the same hooks. So to answer your question directly: one con of keeping derived files in version control is having to set up the above, or possibly letting your derived files slip out of date with their sources.