Should I include .sass-cache with the repo when versioning a web project?

When creating a new project or upgrading an older one, should I conclude the .sass-cache directory in the repo? Since that is always changing and depends on the preprocessor to run wouldn't it be easier to ignore? What are the benefits of including the cache dirs?

Answers


No, you shouldn't include the directory. The general rule is to not include any files generated by some automated process from version control. Including generated files can make merging difficult, adds spurious diffs into commits, and can make your repository awkward to browse, to give a few reasons.

(There are some notable exceptions, like including db/schema.rb or Gemfile.lock for Rails projects.)


Need Your Help

AccessViolationException while reading file header when project not marked as 'Prefer 32 bit'

c# .net winapi

The following code is used to read the first byte from a file header.

Why would a query block if no locks are taken out?

sql sql-server-2008

I ran a query all day yesterday. Takes about 2 hours per run. There were no issues. I was monitoring the locks taken out and checking for blocked processes. There is a process that has to run every...

About UNIX Resources Network

Original, collect and organize Developers related documents, information and materials, contains jQuery, Html, CSS, MySQL, .NET, ASP.NET, SQL, objective-c, iPhone, Ruby on Rails, C, SQL Server, Ruby, Arrays, Regex, ASP.NET MVC, WPF, XML, Ajax, DataBase, and so on.