I am trying to link to another post in my blog. The markdown for both the blog resides in the same folder under _posts. However, when I try to use post_url I always get a build failure with github.
This is how i am declaring it in my markdown.
[Part2 - Details about PyVM and the execution of VM]({% post_url 2016-01-06-PyVyM-Part2 %})
I am adding the code for the post_url in the PyVym-Introduction file.
My .config.yml looks like this.
# Build settings
markdown: redcarpet
pygments: true
permalink: pretty
highlighter: pygments
If I remove the post_url code then there are no build failures. Can someone point me to the mistake here ?
[edited]: github failure email has no error message. It just says build failed.. Exact message below..
"""
The page build failed with the following error:
Page build failed. For more information, see https://help.github.com/articles/troubleshooting-github-pages-build-failures.
"""
Are you using another repository named "pretty" with a gh-pages branch?
Github warns of duplicating these URL's here
If you are having issues with your Jekyll Pages, make sure you are not using categories that are named the same as another project, as this could cause path conflicts. For example: if you have a blog post named 'resume' in your User Page repository and a project named 'resume' with a gh-pages branch, they will conflict with each other.
Related
This is my first GitHub page; I have created repository and even pasted my project into it, but when I enter the URL it gives me 404 error with "There isn't a GitHub Pages site here" description.
My project called 'weather-app' and the URL: https://salehghari.github.io/
So it should be like this: https://salehghari.github.io/weather-app/weatherapp.html
I checked your repository on Github and all the Builds under Actions are marked as Failure with the following error under Deploy:
Error: No uploaded artifact was found!
Under Build I see this:
Error: fatal: No url found for submodule path 'weather-app' in
.gitmodules Error: The process '/usr/bin/git' failed with exit code
128
You are using a submodule but I don't see a clickable link on the repository, are you sure that is correct ? Check if this submodule is correct, there is also an issue on Github Community about this topic.
You need to configure the branch you want to use for your GitHub pages site.
These are the steps you need to follow
I deleted that repo and created another. that un-clickable folder in previous repo was caused the 404 error. Because I had pushed that folder on GitHub once so it means It had had a .git file in it. Thank you every one I appreciate your helps
This is my first attempt at using GH Pages, and I have a pretty simple blog site created with Vuejs.
I've created my repo, then deployed the built code to a gh-pages branch, and the settings are pointed to that branch.
However, I get a WSOD when I try to view my site, and when I look in the console, I get a list of messages that the referenced files can't be found.
When I look in the /static directory in the gh-pages branch, though, all of the files that it says are missing are actually there where they're supposed to be in relation to index.html.
What am I missing that keeps the site from showing?
If you look into the requests, you would find out requesting
https://wonder95.github.io/static/css/app.da01b7b80b6795e91d3ceace476633af.css
This has missed the /smga/ part, and is not what published in your git pages. As the correct link should be
https://wonder95.github.io/smga/static/css/app.da01b7b80b6795e91d3ceace476633af.css
I have a working github pages blog here. -See update below- After adding a new blog post and pushing the update, I received an email from github indicating "Page Build Failure". I can successfully build and serve the site using jekyll locally without issue.
After 22 attempted fixes and subsequent gh build failures, I am at a loss. The base of my blog is built of off this, and I have cloned a fresh copy into my personal blog in an attempt to build fresh from this template. I now get the same build error when pushing this clean template directory.
The only info the github email gives is:
"The page build failed with the following error:
Page build failed"
Has something changed on githubs side that breaks the linked template? Is anyone able to get github to successfully build that template now? I have been successfully updating this blog as recently as August 12th, has something changed in the past couple weeks that has broken my site?
The repo for the site is here
Any help would be greatly appreciated.
-pH+
Update: I attempted to start completely fresh by deleting the working site and following the steps of the template instructions, without success, so the above link will now give a 404 site not found error.
I was unable to figure out why github pages suddenly was unable to build this template, but I've found a work around by compiling the page locally and pushing that to github. This article provides a step by step guides on how to publish to github pages using this technique.
Essentially you need to locally compile and push using the following script in the local Rakefile:
require "rubygems"
require "tmpdir"
require "bundler/setup"
require "jekyll"
# Change your GitHub reponame
GITHUB_REPONAME = "ixti/ixti.github.com"
desc "Generate blog files"
task :generate do
Jekyll::Site.new(Jekyll.configuration({
"source" => ".",
"destination" => "_site"
})).process
end
desc "Generate and publish blog to gh-pages"
task :publish => [:generate] do
Dir.mktmpdir do |tmp|
cp_r "_site/.", tmp
pwd = Dir.pwd
Dir.chdir tmp
system "git init"
system "git add ."
message = "Site updated at #{Time.now.utc}"
system "git commit -m #{message.inspect}"
system "git remote add origin git#github.com:#{GITHUB_REPONAME}.git"
system "git push origin master --force"
Dir.chdir pwd
end
end
When I use a dedicated GitHub page to host this blog the theme works, see here.
However, what I want to do is create this blog as a "Project Page", i.e. a subpage of an organization, in this way.
I've been following the tutorial on how to create a gh-pages branch, provided by GitHub themselves.
In conjunction with the "Host on GitHub in 3 Minutes" tutorial from Jekyll.
I can get it up and running with the basic out-of-the-box theme, but I want to use the "twitter theme", but when I followed the command to install it, i.e. rake theme:install git="https://github.com/jekyllbootstrap/theme-twitter.git" and then pushed to the gh-pages branch, it just completely stripped away all the formatting and now there is no theme at all, see here.
Why did that happen? How can I fix it?
As usual it's a baseurl problem. In _config.yml : set
baseurl: /Description-Logicians-of-EIS
or BASE_PATH if you use Jekyll Bootstrap
If you open up the console in your browser (ctrl + J), you can see the CSS fails to load with a 404.
Failed to load resource: the server responded with a status of 404 (Not Found)
http://eis-bonn.github.io/assets/themes/twitter/css/1.4.0/bootstrap.css
That's probably a good starting point. Where are your css files stored?
Spoiler Alert!
When I visit your repository, the directory pointed to in your header is missing. Instead I find Bootstrap in an entirely different directory.
Good day.
Could you help me with a little problem I am experiencing.
I have a jekyll blog on the github. The problem is after I updated my old post, committed and pushed it, the blog post doesn't show any changes, but I see that the commit has been pushed successfully.
If I run jekyll --server locally, it shows updated blog post and it doesn't report any errors.
I have no jekyll plugins installed.
What am I doing wrong or misunderstanding? Thanks a lot.
Added by Nawaz:
I'm facing exactly same problem. My I pushed added one markdown post and few css, and modified layouts and includes, then I pushed them to github. It is done successfully. My github is showing all the changes in the repository, but the github blog (i.e the generated html posts out of markdown) are still same. No change to them at all. It is showing some posts which doesn't even exist in the repository. But when I do jekyll --server locally, then every update is being shown on my (local) blog hosted at http://localhost:4000.
Please help me!
If your Jekyll site is not rendering properly after you push it to GitHub, it's useful to run Jekyll locally so you can see any parsing errors. In order to do this, you'll want to use the same version that we use.
GitHub's Pages servers currently use Jekyll 0.11.0 with Liquid 2.2.2, and run it using this command:
$ jekyll --pygments --safe
More info
I'm now trying to solve the problems with my pygments highlighting (works locally, doesn't show on github at all, even though I'm receiving mails about succesful build). Findings so far:
Make sure that youre repository' default branch is 'master' (go to your repository Admin page).
Put your Jekyll source files in some other branch, and put the _site content to your master branch. There will be no _config.yml, no YAML front matter so github will render your stuff as is, and you would be building it locally on that other branch. This actually worked for me. It requires some manual labour when moving _site from that other branch to your master, but I'm fine with that - at least I do not have to rely on github build process which seems to be a bit buggy, plus, I can have whatever plugins I wish.
When ever you generate your jekyll site locally for testing, always run jekyll --no-auto --server. This would display if there were any errors encountered during the generation of your site. Also, before generating your site delete _site directory and then run the command as described above.
Let me know if you see any errors as such. We can debug further