Skip to content
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

Do not build a resources folder when no config file present #5896

Closed
Brixy opened this issue Apr 24, 2019 · 0 comments
Closed

Do not build a resources folder when no config file present #5896

Brixy opened this issue Apr 24, 2019 · 0 comments
Milestone

Comments

@Brixy
Copy link

@Brixy Brixy commented Apr 24, 2019

This is not a real issue: When you execute hugo or hugo server in a non-hugo project folder, a folder resources is built anyway.

Maybe Hugo should check for a config.… file or a content folder before building the resources folder?!

I maintain many Hugo projects and therefore this happens from time to time when I do not pay attention.

@bep bep added this to the v0.56 milestone May 21, 2019
@bep bep removed this from the v0.56 milestone Jul 26, 2019
@bep bep added this to the v0.57 milestone Jul 26, 2019
@bep bep removed this from the v0.57 milestone Jul 31, 2019
@bep bep added this to the v0.58 milestone Jul 31, 2019
@bep bep removed this from the v0.58 milestone Aug 13, 2019
@bep bep added this to the v0.59 milestone Aug 13, 2019
@bep bep removed this from the v0.59 milestone Sep 6, 2019
@bep bep added this to the v0.60 milestone Sep 6, 2019
ollien added a commit to ollien/hugo that referenced this issue Oct 15, 2019
@bep bep removed this from the v0.60 milestone Oct 21, 2019
@bep bep added this to the v0.61 milestone Oct 21, 2019
@bep bep closed this in e6aa6ed Oct 21, 2019
@anthonyfok anthonyfok removed this from the v0.61 milestone Nov 1, 2019
@anthonyfok anthonyfok added this to the v0.59.1 milestone Nov 1, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Linked pull requests

Successfully merging a pull request may close this issue.

None yet
3 participants