-
-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Jekyll keeps regenerating when output folder already exists. #340
Comments
I can confirm this behavior. It appears to be a problem with directory_watcher, there is currently an open issue (#8) on that repo suggesting adding an ignore glob option that TwP is supporting. |
As soon as my pull request solving issue TwP/directory_watcher#8 will be approved I'll try to fix this behaviour. |
Any news on this? I'm getting the same using Jekyll 0.11.2 |
Ah didn't catch the part about removing the output folder before running Jekyll auto. Did that and it solves it but obviously nice to have it fixed. |
I have same problem, |
Now, I don't put destination: /tmp/project/public Now Fixed, but not pretty. |
I've had this same behavior with _public too. |
Fix in #862. |
I don't know why it is closed. I get this problem on one of my computers. Strangely not on the second one, but no idea what makes the difference... both are Linux Ubuntu. |
I'm getting this issue on debian wheezy. Jekyll just keeps regenerating endlessly |
When I start Jekyll using
jekyll --auto
and the output folder (public
in my case) already exists, it keeps regenerating some files:When I remove the
public
folder and restart Jekyll, it works fine:Using Jekyll 0.10.0
The text was updated successfully, but these errors were encountered: