Closed RehanSaeed closed 8 years ago
The gulp-newer
plugin works by comparing modification times of source files to modification times of destination files. If you have both source and destination files checked into git, git should only update modification times when a file is changed - so things should just work. But I'm guessing that since you opened this issue, you are not getting the behavior you expect.
I'm trying to evaluate a few NPM plugins that all claim to do the same or similar thing. In my case my source and destination images are both the same file, just minified versions. So I guess, gulp-newer is not the right tool in this case?
If you are overwriting your source files with your destination content, then gulp-newer
is not going to be of use.
Great, thanks!
I want to use gulp-imagemin which is a very slow and processor intensive task and I am working in a team environment using Git. How can I make sure that an image is only ever processed once in my entire team? Where does gulp-changed-in-place save it's change log? Can it be checked-in to Git?