I used to use Github pages to get a live demo for any finished project I pushed to GitHub and it was working properly and now it is not working every time I go to the repository setting and to pages I change the branch from none to main and the save button is not clickable on any new repository I have created recently I asked on the Github community and did not get any solution for this problem so, please help me solve this problem
enter image description here
enter image description here
Recently in Chrome Dev Tools when I make local CSS changes, then refresh the page, the CSS changes stay. In the past, local CSS changes were not persisted, but the page would refresh to its original state as originally served from the server.
Is there a way to have Chrome Dev Tools behave as it used to, removing the custom CSS changes on page reload?
While I was editing README.md in one of my repositories, the process blocked somehow.
Since then, when I access that repository, status stays in 'Fetching latest commit… ' and I am not able to upload any files or edit them on the web.
The other repositories work. I do not have this repository on my computer (i have the files obviously), and the system does not allow me to clone it, not even delete it.
What can I do to regain access?
THOUGH DEFINITELY it does not the answer your question, but I want to post a solution for whom have the same problem but because of different reason.
For Forecomers having the issue
I had the same issue(just reached this question by googling), and I remembered disabling the javascript of my browser. Why don't you enable the javascript of your browser and refreshing the page? In my case the problem was solved after enabling javascript.
I have a github project and I am using Github pages.
I can see the newest code changes on the gh-pages branch on my github account(web-interface) but the same changes are not visible on the Github page.
Note : I have given it more than a day to assuming that it will take some time for the actual deployment. In fact github.org mentions that it might take upto half an hour. So I am not sure why it is taking so long.
The issue was because of a browser cache. Clear your browser cache and you should see the changes after half an hour.
Have you checked your email? There could be errors in your code which prevent page builds. See https://help.github.com/categories/github-pages-troubleshooting/ for more.
I am trying to use coveralls.io to show a coverage badge for my tests, but the coverage badge is stuck on "unknown".
The relevant repo is here: https://github.com/cfogelberg/grunt-set-app-mode
When I look at coveralls.io for that repo I see the same "coverage: unknown" status: coveralls.io/r/cfogelberg/grunt-set-app-mode
However, the individual builds are being correctly sent to coveralls.io: https://coveralls.io/builds/788669
What am I missing?
If clearing your local cache isn't fixing the image, the problem is likely that it was cached by Github as a part of their image URL anonymization process.
You can force Github to clear their cache of the image with the following curl command. Change the example URL to the one from the your repo, it will always be https://camo.githubusercontent.com/ followed by a long hash.
curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
Source: GitHub Help: About anonymized image URLs
What am I missing?
It's possible that your browser cached the image. I realized this was happening to me recently. I couldn't understand why my badge said one thing on my github page, but something different on the badge's website.
Now I tend to check websites in a Chrome incognito window so I don't have the cache to worry about.
In my case, I had the code coverage outdated in my coveralls badge with this Markdown snippet:
[](https://coveralls.io/github/user-repo/user-project?branch=master)
But when I removed the branch parameter of the first URL, the coverage gets updated!
[](https://coveralls.io/github/user-repo/user-project?branch=master)
Update:
My first solution didn't work the second time though. So I reverted it, and resorted to changing the badge type from SVG to PNG.
[](https://coveralls.io/github/user-repo/user-project?branch=master)
Since posting this question I have pushed more commits and rerun the coveralls task a number of times and the coverage badge now works:
https://github.com/cfogelberg/grunt-set-app-mode/compare/4FB59ACC...58E23E5373
It is not clear why it works now and didn't earlier. coveralls has been added to the default task since the previous failed build on coveralls. However, it was added to the default task and pushed to Github earlier than the next build on coveralls, which only changes the README.md file (fixing a link to a david-dm.org badge).
I'm afraid this isn't really a "solution" as such and I would still love to know (not sure why/who voted the question down), but in any case I hope this information is useful to someone else in the future.
Your browser cached the badge image. To force an update, hold SHIFT while reloading your browser tab (on Brave on macOS, I do this via CMD + R).
For me the problem was that the image was cached by github, not my own browser. There is a fix documented here that worked:
I added 'kill_cache=1' in the image url
ex: src="https://coveralls.io/repos/github/spread-the-code/git-commiter-nodejs/badge.svg?branch=master&kill_cache=1" />
https://github.com/lemurheavy/coveralls-public/issues/1065
Add a queryString param to the badge image URL, Here is the answer https://github.com/lemurheavy/coveralls-public/issues/1065#issuecomment-435494495
I've come arround this issue adding a PURGE request to purge GitHub's cached copy of the badge at the end of a my github actions workflow:
$ curl -X PURGE https://camo.githubusercontent.com/4d04abe0044d94fefcf9af2133223....
i 've used the http-request-action :
- name: refresh coverage badge
uses: fjogeleit/http-request-action#master
with:
url: https://camo.githubusercontent.com/12c4fcb3b21fbb2a725fc61449fb1b91e972c4c8a2baaf5904936d8e334bdbe8/68747470733a2f2f636f766572616c6c732e696f2f7265706f732f6769746875622f62336230302f63736c792f62616467652e7376673f6272616e63683d64657626736572766963653d676974687562
method: PURGE
I have tried other proposals here, and none of them seems to work.
Install disable Cookies chrome extension from here.
Go to your github project, press disable cookies, and then restore them back.
coveralls.io badge should be updated after that.
Suspect same problem is applicable also to normal users as well.
In my case image failed to refresh no manner how many times I've pressed reload, used purge or so other tricks (did not want to clear history).
Also anonymous web browsing sometimes helps.
Please note that coveralls.io report takes time to be processed, so need to wait couple of minutes at least. (Can be checked from coveralls.io site).
#iamdefinitelyahuman Answer helped me, but I would like to add some more things that weren't clear to me.
I had the same issue. My coveralls status badge was showing an old coverage percentage. The reason was that the badge was cached by GitHub so I had to clean it using a curl command.
In the beginning, I didn't realize where to get the URL "https://camo.githubusercontent.com/...". After some time I understood that it is the badge image path that can be taken by inspecting the image element.
Then I opened Powershell which was a mistake and run the command:
curl -X PURGE https://camo.githubusercontent.com/a4550375d0d4b6f1b363909b2aeeb2827303e07388abe00c0662700f1514fef5/68747470733a2f2f636f766572616c6c732e696f2f7265706f732f6769746875622f4d69636861656c5a61736c6176736b792f736f6369616c2d6576656e742d6d616e616765722f62616467652e737667.
And I got this error:
Then I tried to run this command in CMD and it worked properly.
{ "status": "ok", "id": "10525-1659579296-180434" }.
Then I still didn't see it on my browser as it was my browser cache issue. I knew it is a browser cache as I could see the new coverage percentage in Incognito.
Lastly, I cleaned the cache of my browser by opening the developer's tools (F12) => Right-click on the refresh button => Empty Cache and Hard Reload. And, that I could see the percentage updated in my browser as well.