Github pages not giving site url after trying to republish the site from repo #164286
Replies: 4 comments 2 replies
-
It may be a caching or deployment delay issue. Here are a few quick checks: ✅ GitHub Pages settings: Ensure it's set to the correct branch (main) and root folder. 🔤 Case sensitivity: File names in HTML must exactly match the actual files (e.g., style.css ≠ Style.css). 🔄 Clear cache: Use Ctrl+Shift+R or try incognito mode. 🌐 Check site URL: Go to Settings > Pages to see if the URL is available. 🚦 Trigger redeploy: Make a minor commit (e.g., edit README.md) to re-trigger deployment. If it still doesn’t work, check for errors in the Pages section or GitHub Actions tab. |
Beta Was this translation helpful? Give feedback.
-
You likely faced this because initially only index.html was pushed, so CSS/JS weren’t loading. Even after adding them later and correcting paths, GitHub Pages may have cached the old version. Unpublishing and republishing resets it, but it can take some time. Ensure the correct branch and folder are selected in Settings > Pages, filenames match exactly (case-sensitive), and clear browser cache or try incognito. If the site link still doesn’t appear after republishing, wait a bit more or check for build errors in the Actions tab. |
Beta Was this translation helpful? Give feedback.
-
Making a small commit worked ,(≧∇≦)ノ |
Beta Was this translation helpful? Give feedback.
-
Check GitHub Pages Settings: Ensure that GitHub Pages is enabled for your repository and set to the correct branch (often main or master) in the repository settings. Verify that the source directory is correctly set if you have specific requirements (like a /docs folder or a specific branch). Verify File Changes: Double-check that the changes you made to your CSS and JS files are committed and pushed to the correct branch on GitHub. Cache Clearing: Sometimes, browsers cache old versions of websites. Try clearing your browser cache or accessing your site in an incognito/private browsing window to bypass any cached content. GitHub Pages Build Status: Check the GitHub Actions or GitHub Pages section in your repository settings to see if there are any build errors or warnings that might be preventing the site from deploying. Commit and Push: Ensure that after making changes, you commit and push them to GitHub. GitHub Pages serves content directly from the repository, so changes must be committed to the repository for them to appear on the live site. Wait and Retry: Sometimes, GitHub Pages can take a bit of time to update, especially after unpublishing and republishing. Give it some time (up to 24 hours in some cases) and then check again. |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Select Topic Area
Question
Body
First i put only index.html file ,launched github pages my css and js were not showing coz forgot adding them in repo .Then i added but my website was not reflecting the changes even i corrected the paths and casing of css and js files in index.html then i unpublishedd the site and tried publishing it again, hoping it might work but it's been 8+ hours and github has not provided me with a site link
Beta Was this translation helpful? Give feedback.
All reactions