-
Notifications
You must be signed in to change notification settings - Fork 11.6k
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
website not building when url
under _config.yml
is left blank
#422
Comments
Ok, I can reproduce this on
Should I add the url from now on, even if deploying with github pages? In the
Thanks! |
url
under _config.yml
is left blank
@p-costa, thanks for brining this up. correct, after adding target blank plugin in #404, it is now required to specify |
Perfect, thank you very much! I updated my webpage accordingly and the issue seems settled. Please feel free to close the issue! |
Just wanted to update on this, I spent the last two weeks finding a solution to this bug! I finally solved it a few minutes ago, and then found this issue here. Can we have clear README instructions for the previous al-folio users that they need to fill this when updating the code? |
I have run into this issue. Now, although I set my url: https://tirtharajdash.github.io, while I deploy (using ./bin/deploy --user), it runs into the same issue. And, then when I checked _config.yml, the url: #https://tirtharajdash.github.io (that is, the deploy code is commenting the url out). What am I doing wrong? |
Acknowledge the following
[For usage questions, please post in the Discussions instead of raising an issue.]
Describe the bug
The website deployment in CI is failing, with my website in sync with 533bed5. I wonder if this is a bug on
al-folio
, or something I should change on my end. Here is the log:I hope this is enough information (the website is in a private repository). Thanks in advance!
EDIT: I manage to visualize the website with
bundle exec jekyll serve
, but withbundle exec jekyll build
I get the same error in my local machine as in the CI.The text was updated successfully, but these errors were encountered: