I have many private repositories on my GitHub. Until yesterday I was able to commit to any repository on my GitHub. But today, I am trying to change the readme.md file in my repository, I am not able to see the preview and also not able to commit as the commit button is disabled.
Actually, later I saw that I am unable to commit any file in chrome browser only , but I can commit any file in other browser (Microsoft Edge) . And also, I am able to commit from my IDE (MS Visual Studio) . So, My question is that , why I am unable to commit from Chrome only.
I found solution for this problem:
Problem is occurring due to I Added extension in chrome i.e. ad blocker extension.
So, I removed that extension and problem is solved.
Make sure you have modified/updated any contents in the README.md file. If there is no changes in the file, "Commit Changes" but will be disabled.
I had the same problem until I deactivated/trusted Ghostery for uniquely github.com
Image shows active Ghostery:
I had the same issue. I found by adding the file name you are going to create in the url can solve the issue.
yourusername/new-file-name.html. (in main)
I am trying to deploy a github.io blog but having an issue with build and deployment. I can build the files without any issue on local server, but when I try to publish it on github server by pushing it, it throws a build and deployment error saying:
Error: Error: No uploaded artifact was found!
Here's my git repo link for more info: https://github.com/dailyole/dailyole.github.io/runs/4677505925?check_suite_focus=true
I was able to publish the same files on github.io without an issue a few weeks ago, but it throws an error now.
In my case my problem was caused by some bad submodule references:
https://github.com/catalin-hritcu/catalin-hritcu.github.io/actions/runs/1643762494
No url found for submodule path 'teaching/epit2018' in .gitmodules
This seems to be a common issue these days:
https://github.community/t/failed-to-publish-static-site-spa-with-submodules/219880
It fixed it with some commands like this:
git rm --cached teaching/epit2018
This doesn't seem the problem for you though.
solved it by change the theme of blog.
methed 1: change it in web by settings.
On GitHub, navigate to your site's repository.
Under your repository name, click Settings.
settings
In the "Code and automation" section of the sidebar, click "Pages",
then, click "change theme"
change theme
select one theme, and click "select theme"
select
methed 2: change in the file
vim _config.yml
change the line
theme: jekyll-text-theme
to a new theme, like
theme: jekyll-theme-cayman
: sorry for I need at least 10 reputation to post images
Realized this issue occurs when there is an empty submodule in your GitHub repo. Removed the empty submodule and it's working now.
As far as I can see, your problem is different than mine though:
https://github.com/dailyole/dailyole.github.io/runs/4677504175?check_suite_focus=true
github-pages 223 | Error: The jekyll-theme-hydejack theme could not be found.
I also meet the question, and my git repo is: github-pages 223 | Error: File to import not found or unreadable: mixins/reset-filter.
Then I see the path that have the problem, I found this file isn't uploaded. The folder contains too many files and I didn't check it again. May be you need to check if some files are not uploaded.
I have installed GitHub Desktop as the uploaded local project tool, I uploaded a project "F:/test", and it could show successful in my GitHub homepage, then I delete this repository.
But I re-publish this project to GitHub.
Github Desktop shows this history of the repository, and prompt error
The repository does not seem to exist anymore.
You may not have [enter access, or it may have been deleted or renamed
How can I get past this error message?
This error was keeps on occurring to me. Turn out I was not added as the Contributor on the GitHub project.
The repo owner should be able to see and list of Contributor for the project. You can request him to add you in contributor list and this error will disappear.
I was facing the same issue, I simply sign out from Github Desktop app in File > options > Signout
In my case I accidentally changed the push Url, so I executed:
git remote set-url --push origin https://github.com/username/repo.git
After that I checked with:
git remote show origin
your Fetch Url and Push Url must look like the same URL where you cloned the project.
As shown in this error, it is the result of an invalid local path. Either because it includes invalid characters, or because you don't have write/admin access to it (read access is not enough).
If you can, clone again that repo in a different path and open it with GitHub Desktop, and see if the issue persists.
I had the same issue. I deleted my repository from remote as well and then recreated.
If you aren't worried about the change trace being lost, then you can simply remove the .git folder (you will need to enable hidden files in windows) and then re-initialize the repository in the project folder.
This resolved the problem for me!
In my case I have used more than one account. Just sign out from GitHub Desktop and sign in back to the specific account. You might sign out any logged GitHub session on the default web browser if the account is not what you want.
Since I had a forked repository, I had spelled my url wrong in
github desktop -> repository -> repository settings...
I had a link called github.com/myname/myproject.it
but instead of it I hade to write git.
github.com/myname/myproject.git
I was logged in with the wrong account! I had to sign out of Github in the browser first, then sign out in Github Desktop and re-sign in
Here is my GitHub repository on the gh-pages branch.
Everything looks good, I have my index.html, my CSS, JS and pictures folders.
But when I access http://roine.github.com/p1 I get HTTP 404 not found.
Any explanation and solution?
I had just one commit with all my files. I pushed an empty commit, refreshed the page and it worked.
git commit --allow-empty -m "Trigger rebuild"
git push
If this doesn't work, as #Hendrikto pointed out in the comments, check out the Github status page and make sure GitHub Pages are operational.
I did all the tricks on my repo to fix page 404 on Github Page (https://eq19.github.io/) but it kept 404'ing.
Finaly found that my browser hardly keep the 10 minutes cache before it up on the web.
Just add /index.html into the end of URL then it showed up and solved the case.
https://username.github.io/{repoName}/index.html
In my case, I had folders whose names started with _ (like _css and _js), which GH Pages ignores as per Jekyll processing rules. If you don't use Jekyll, the workaround is to place a file named .nojekyll in the root directory. Otherwise, you can remove the underscores from these folders
Four months ago I have contacted the support and they told me it was a problem on their side, they have temporarily fix it (for the current commit).
Today I tried again
I deleted the gh-pages branch on github
git push origin --delete gh-pages
I deleted the gh-pages branch on local
git branch -D gh-pages
I reinitialized git
git init
I recreated the branch on local
git branch gh-pages
I pushed the gh-pages branch to github
git push origin gh-pages
Works fine, I can finally update my files on the page.
If you haven't already, choose a Jekyll theme in your GitHub Pages settings tab. Apparently this is required even if you're not using Jekyll for your Pages site.
I had the same issue after forking a repo with a gh-pages branch. I was able to fix by simply pushing a new commit (just whitespace in index.html) to my fork's gh-pages branch.
In my case on 8/Aug/2017
if your user page is https://github.com/mgravell, you repo name must be
mgravell.github.io
under root, create a file index.html
under root, create a folder docs, create a file
CNAME under docs (note: NO extension like .txt, make sure your file
system shows extension)
gh-pages branch is optional, master branch is sufficient
more: check official docs here: https://help.github.com/articles/configuring-a-publishing-source-for-github-pages/
Just wait about ten minutes to one hour. If it still doesn't work, contact github. Usually it's the problem at their end.
But, if you're in a hurry, you can try to open by adding "?" question mark at the end of URL. It force query to search for the resource. Like this:
http://roine.github.com/p1?
In my case the browser had a previous cached version of my app. To avoid getting the cached version, access you url using a random query string:
https://{{your-username}}.github.io/{{your-repository}}?randomquery
My pages also kept 404'ing. Contacted support, and they pointed out that the url is case sensitive; solved my issue.
in my case i had to go to project settings and enable the github pages. The default is off
If you saw 404 even everything looks right, try switching https/http.
The original question has the url wrong, usually you can check repo settings and found the correct url for generated site.
However I have everything set up correctly, and the setting page said it's published, then I still saw 404.
Thanks for the comment of #Rohit Suthar (though that comment was to use https), I changed the url to http and it worked, then https worked too.
Add the following in the beginning of the index.html file
<!DOCTYPE html>
In my case in react was necessary to select the gh-pages branch:
I was facing the same issue, after trying most of the methods mentioned above I couldn't get the solution. In my case the issue of because of Github changing the name of master to main branch.
Go to Setting -> go to GitHub Pages section and change the branch to main:
to
Save it and select a theme, and the website is live.
If you are sure that your structure is correct, just push an empty commit or update the index.html file with some space, it works!
I had this exact problem with typedocs. The README.md worked but none of the actual docs generated by my doc strings displayed, I just got a 404 Github Pages screen.
To fix this, just place a empty file in your /docs directory (or wherever you generate your docs) & call it .nojekyll
To confirm, your file structure should now look like:
./docs/.nojekyll # plus all your generated docs
Push this up to your remote Github repo and your links etc should work now.
Also make sure you have selected in your Github settings:
Settings -> Github Pages -> Source -> master brach /docs folder
Depending on your doc framework, you probably have to recreate this file each time you update your docs, this is an example of using typedocs & creating the .nojekyll file each time in a package.json file:
# package.json
"scripts": {
"typedoc": "typedoc --out docs src && touch docs/.nojekyll"
},
The solution for me was to set right the homepage in package.json.
My project name is monsters-rolodex and I am publishing from console gh-pages -d build.
"homepage": "https://github.com/monsters-rolodex",
The project was built assuming it is hosted at /monsters-rolodex/.
Before it didn't work because in the homepage url I included my github username.
I got the site to work by deleting the "username.github.io" folder on my computer going through the steps again, including changing the index/html file.
My mistake (I think) is that i initially cloned "https://github.com/username/username.github.io.git" instead of https://github.com/username/username.github.io (no ".git")
In my case, all the suggestions above were correct. I had most pages working except few that were returning 404 even though the markdown files are there and they seemed correct. Here is what fixed it for me on these pages:
On one page, there were a few special characters that are not part of UTF-8 and I think that's why GitHub pages was not able to render them. Updating/removing these char and pushing a new commit fixed it.
On another page, I found that there were apostrophes ' surrounding the title, I removed them and the page content started showing fine
Another variant of this error:
I set up my first Github page after a tutorial but gave the file readme.md a - from my perspective - more meaningful name: welcome.md.
That was a fatal mistake:
We’ll use your README file as the site’s index if you don’t have an
index.md (or index.html), not dissimilar from when you browse to a
repository on GitHub.
from Publishing with GitHub Pages, now as easy as 1, 2, 3
I was then able to access my website page using the published at link specified under Repository / Settings / GitHub Pages followed by welcome.html or shorter welcome.
For some reason, the deployment of the GitHub pages stopped working today (2020-may-05). Previously I did not have any html, only md files. I tried to create an index.html and it published the page immediately. After removal of index.html, the publication keeps working.
I was following this YT video. So, when I ran the command in my terminal, it pushed the code to gh-pages branch already. Then I pushed to the master branch. It was giving me 404 error.
Then I swapped the branch to master and then again reverted to gh-pages and now the error is gone. It's pointing to the index.html even if it's not in the URL.
I bound my domain before this problem appeared. I committed and pushed the branch gh-pages and it solved my problem. New commits force jekyll to rebuild your pages.
In my case, the URL was quite long. So, I guess there is a limit. I put it to my custom subdomain and it worked.
On a private repo, when I first added and pushed my gh-pages branch to github, the settings for github pages automatically changed to indicate that the gh-pages branch would be published, but there no green or blue bar with the github.io url and no custom domain options.
It wasn't until I switched the source to master and quickly switched the source back to gh-pages that it actually updated with the green bar that contains the published url.
Your GitHub Pages is available at http://roine.github.io/p1 instead of http://roine.github.com/p1.
By the way, you can fix your project's description.
In my case it was that I had recently set up a custom domain for GitHub pages, but GitHub had forgotten my custom domain under (repo)<name>.github.io / Settings / Pages.
I added the custom domain again and then it immediately started working.
Go to settings section of your repository and choose master branch at the Source section and click save button after that refresh the page and you will be able to see the link of your page!.
I faced this problem (404) too and the root cause was my file was named INDEX.md. I was developing on Windows and my local Jekyll site worked (since Windows treats file names case insensitive by default). When pushed to Github, it didn't work. Once I renamed the INDEX.md to index.md, things worked well.
I am very new to GIT and am trying to check out some example projects from the eclipse.org git repositories. I just installed the EGit plugin and have reached a roadblock when trying to enter the correct parameters at the "Import Projects from Git" menu.
The location of the examples I wish to check out are located here.
http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/tree/dsf
However I am unsure how to create the correct URI, Host, and Repository Path from this url.
I would like to be able to explore the different repositories listed on that page (for example the org.eclipse.cdt.examples.dsf folder) and checkout those projects, however I just can't figure out what the correct git url for this would be.
I'm coming from SVN, so I am sure I got some terminology wrong. I have been following this tutorial for using git: http://wiki.eclipse.org/EGit/User_Guide#Cloning_Remote_Repositories
If you click on "Summary" in the page you mention (http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/tree/dsf), you will get a page (http://git.eclipse.org/c/cdt/org.eclipse.cdt.git/) which displays, at the bottom (you need to scroll down), the clone addresses:
Clone
git://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
ssh://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
http://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
You can use one of those addresses to clone from Egit: see "Cloning Remote Repositories" from the user manual.
This page contains documentation from the Eclipse project about cloning their git repositories. They show an explicit example for the org.eclipse.cdt.git repository. You can use either this:
git clone git://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
Or this:
git clone http://git.eclipse.org/gitroot/cdt/org.eclipse.cdt.git
I usually use git:// URLs when they're available. They used to be faster, but this may not be true anymore. Either should work just fine.
In general, it looks like repositories are available from git://git.eclipse.org/gitroot/<PROJECT>/<REPO>, where it's up to you to correctly substitute <PROJECT> and <REPO>.