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
This is as old as the ages, and the problem existed in the Yacc world long before CSS was invented. Keep both the SASS and the resulting CSS files in version control. Good: More predictable, eas...
Answer
#1: Initial revision
by
. .
·
2020-10-22T16:12:51Z (about 4 years ago)
This is as old as the ages, and the problem existed in the Yacc world long before CSS was invented. > Keep both the SASS and the resulting CSS files in version control. Good: More predictable, easier to handle deployment. Less toolchain is necessary for building. Fewer dependencies for certain users. > Only storing the SASS files in version control. Good: Saves space. --- Useless trivia, but amazing: [currently Bison kind of advices shipping generated *.c docs along with source *.y docs][0]. [0]: https://lists.gnu.org/archive/html/bison-patches/2020-10/msg00014.html