I've just pushed a change to my repository and have received a message warning me that my Jekyll build has failed. The page is still online, but in Settings for the repository I still find an error message instead of the usual "your page is online" and the URL green message. However, I have put .nojekyll files both in the master and docs folders (I'm using docs for the page), so of course I wouldn't expect the build to begin in the first place. Is this normal behaviour or some kind of bug? Is it an error on my part? This is the repository:
Thank you very much!
Thanks for being here! I want to confirm that I see your site is up, but if you're still seeing this error or other strangeness, I'd recommend you write in to private support. They'll be able to dive into this a bit deeper and help discover what the underlying issue might be.
So trying to change this url: roberthamill.graphics to roberthamill.design for SEO purposes.
Did all the uploads and its giving me a 404
Feel free to check out the files https://github.com/rbhamill/roberthamill.design
You'll either need to create a gh-pages branch on the roberthamill.design repo (as mentioned above), or you'll need to create a rbhamill.github.io repo.
Then you can point your custom domain at it using this guide: https://help.github.com/articles/using-a-custom-domain-with-github-pages/ .
I follow exactly the tutorial of deploying the site on git-pages, and even have gh-pages branch, but error happens again and again. although i have in my Git Pages settings:
Your site is ready to be published at https://temavrn.github.io/my_site/.
and i tried hexo-deployer git, but nothing works
should i try to install git desktop?
this is my repo https://github.com/temavrn/my_site
I'm not exactly sure what you mean regarding the username.github.io requirement. Are you asking about custom domains? If so, you can follow these instructions to set up a custom domain for your GitHub Pages site.
As for updating your site, the content should update whenever you make a change and push it up to your GitHub Pages branch. However, this can take a few minutes to process your changes and re-render the site. If your changes still aren't showing up, I recommend checking out these steps for troubleshooting GitHub Pages builds and see if that helps or anything.
Thanks for reaching out about this! In short, it’s not possible to manually assign a content-type for files on GitHub Pages.
GitHub Pages supports more than 750 MIME types across 1,000s of file extensions. The list of supported MIME types is generated from the mime-db project, which aggregates MIME types from the Apache and Nginx projects as well as the official IANA list of internet content types.
If you wish to contribute a new mime type to mime-db please see the contributing instructions here.
I hope this helps!
I have accidentally pushed my master branch in the gh-pages branch of one of my repos, and this have added all the commits which are now counted twice in my contributions (master and gh-pages branches). Even after I forced push a single commit to the gh-pages branch, all the commits are still counted. I would rather have a proper count because here my contributions are overrated. Is it possible to remove commits counts or they can only be added ?
For your information, I found this page in GitHub Help, which explains the difference between author date and commit date:
"In Git, the author date is when someone first creates a commit with git commit. The commit date is identical to the author date unless someone changes the commit date by using git commit --amend, a force push, a rebase, or other Git commands.
On your profile page, the author date is used to calculate when a commit was made. Whereas, in a repository, the commit date is used to calculate when a commit was made in the repository."
So after I pushed a single commit to the gh-pages branch, the author dates of the commits I had overridden were still somewhere and thus counted in my contributions, whereas the commit date were erased with the commits and thus I did not see them in the repo. At least this is what I have understood.
So I deleted the gh-pages branch on both local and remote repos, pushed a new clean gh-pages branch and now everything works as expected.
I made a blog with Github Pages and Jekyll. For my Persian blog, i made a repository named farsi and converted it to a page so it would be available at https://alireza.one/farsi. Now sometmes when i open my blog by my iphone, page doesn't open and it appears like a file and it wants to open in Telegram messenger.
Can somebody tell me what should i do?
It looks fine to me, from the computer and from my phone(I have an iPhone as well). Perhaps you refreshed it too quickly after you just changed the name of the repository? Sometimes, it takes a while to update.
I tried to follow similar posts on the community forum but nothing really worked so far:
also found some step-by-step instructions in this Gist: https://gist.github.com/cvan/8630f847f579f90e0c014dc5199c337b but I'm not sure what I'm missing.
Here's my github page: https://github.com/akoskm/akoskm.github.io and here is my DNS config from godaddy:
the top A record is added when I'm setting up the http->https forward:
even if the box Update my nameservers and DNS settings to support this change is unchecked.
Any other GitHub page users facing the same problem?
CNAME records are for subdomains, such as www.example.com. A records are for apex domains, such as example.com. It appears from what you're showing here, that you've configured both the A records and CNAME records to point to the apex domain. This may be what is causing your problem. I would recommend simply starting with the CNAME subdomain records, since those are easiest to get working. Once that is working properly, then experiment with the apex domain stuff.
I hope that helps!
I have published http://cppalliance.com from https://github.com/CPPAlliance/cppalliance.github.io
As you can see, there's a CNAME. Everything is great, the page renders as it should and when I push changes the pages get rebuilt.
However, multiple people are working on this now. Similarly to how a team might collaborate on building a C++ program, I have made a fork of the repository in my personal account:
Now I can make changes, rebase, squash, fold, and generally arrange the branch any way that I want before submitting it as a pull request to the upstream repository. A problem arises, how to preview the changes before the merge? Well, I can visit the Project GitHub Page:
I can see some of my content, but where did the style sheet go? Is this because the URI is not a root target?
I am also getting an error in my email about the CNAME being taken. Well, that makes sense. We can't have every fork also be aliased to cppalliance.com. But I also don't want to get this error every time. I could delete the CNAME file from my fork, but that would create headaches when merging the submitted pull request to the upstream repository. Is there a way to disable the CNAME from my fork's Project's settings? I don't see it - consider adding it.
Anyway, I would very much like to get to a point where the team members can preview change to their individual forks before submitting the pull request, using the wonderful GitHub Project Pages mechanism described in the docs.
I'm afraid to say that GitHub Pages sites with custom domains don't play especially well with forks at the moment. For now, there isn't a way to supress the CNAME warnings, other than configuring an email filter on your end to automatically archive these messages. It's not the most elegant solution, but it does work.
Another alternative is to bypass publishing the fork altogether, and instead use a local Jekyll environment to test changes offline. We have documentation here on how to get that set up:
Of course, we're aware that this could be better, and it is something that we'd like to improve in the future. I can't make any promises, but I'll certainly communicate your observations to our team!
Finally, there's the CSS issue you mentioned – this isn't specific to GitHub Pages, but is rather a general HTML concept. At the moment, the CSS file is referenced as:
The leading slash before "css" there represents the root of the published URL. This works just fine when the site is published at http://cppalliance.com, but causes trouble when published at https://username.github.io/cppalliance.github.io. That's because the slash will end up referring to https://username.github.io (the root of the domain), not the relevant "cppalliance.github.io" subdirectory, where the CSS file is actually stored.
The simplest solution to this trouble is to remove the leading slash, leaving you with the following:
This construction tells the browser to look for a "css" folder within whatever directory the index.html page is being published from, and should therefore function perfectly regardless of which domain the site is published at. You can learn more about HTML file paths here:
I hope that helps!
Ok, this is my github md file in repo:
when displayed in github it all works.
But when i show it in "pages" some of the formating are not displayed.
As you se, instad of converting to html it display the markup taggs like normal content.
How can i fix this? I want it to show correct both in the repositorie and page.
I've submitted a Pull Request with some changes I recommend.
The reason for the differences in rendering is because github.com uses CommonMark for its Markdown rendering whereas GitHub Pages uses Jekyll and Kramdown for its Markdown rendering. Because the two components use different rendering engines, there are differences in interpretation of Markdown documents. However, incorporating the changes I suggested in the PR above should take care of those problems for you.
I hope that helps!
Apologies if this is a noob question but I really am lost here - I have created the following Repo https://github.com/m0chan/m0chan.github.io and enabled GitPages and if I visit m0chan.github.io it appears as it should! Great! What's the problem?
Well I have created a folder called 'HackTheBox' where I will store reports of boxes I have completed in markdown format. I would like to be able to visit m0chan.github.io/HackTheBox/Valentine.md and it appears with the nice GitPage/Theme however it does not.... It is displaying in plain text?
The file name is ValentineHTB.md, which is important 😀 GitHub Pages converts your Markdown files to HTML. So if you want to see the `ValentineHTB.md` file on your GitHub Pages site, it is at https://m0chan.github.io/HackTheBox/ValentineHTB.html (note the `.html` extension instead of `.md`)
I hope that helps!