Am I likely doing something wrong since the GitHub repo of the same files does not deploy correctly? It would be great to be able to link GitHub so that I can have continuous deployment. Thank you for your help!
Let’s ignore the working site at the moment and focus on the one that’s not working. When you say it “wont deploy”, what happens exactly? Do you get a deploy error? Can you paste a log please of a deploy that doesn’t work?
Hey @perry thanks for getting back to me. Exactly, the site at - [https://silly-shaw-c6587d.netlify.app does not load correctly when I update files, commit and push to GitHub.
I do not get a deploy error, jus the site is not visible when I click the link at : https://silly-shaw-c6587d.netlify.app . It says the link is broken. Below is the deploy log. I suspect this is likely an obvious mistake, my apologies, I am new to this!
6:59:54 PM: Build ready to start
6:59:56 PM: build-image version: 30f629161c0736b1a3ecd8b418e5eeffab5c0faf
6:59:56 PM: build-image tag: v3.3.14
6:59:56 PM: buildbot version: c59536cd5af8d84bd2f02c6af4027561b250018a
6:59:56 PM: Fetching cached dependencies
6:59:56 PM: Starting to download cache of 7.1KB
6:59:56 PM: Finished downloading cache in 163.129586ms
6:59:56 PM: Starting to extract cache
6:59:56 PM: Finished extracting cache in 7.807568ms
6:59:56 PM: Finished fetching cache in 171.233325ms
6:59:56 PM: Starting to prepare the repo for build
6:59:57 PM: Preparing Git Reference refs/heads/master
6:59:57 PM: No build command found, continuing to publishing
6:59:57 PM: Starting to deploy site from ‘’
6:59:57 PM: Creating deploy tree
6:59:57 PM: Creating deploy upload records
6:59:57 PM: Starting post processing
6:59:57 PM: 0 new files to upload
6:59:57 PM: 0 new functions to upload
6:59:57 PM: Post processing done
6:59:58 PM: Site is live
6:59:58 PM: Finished processing build request in 2.231782398s
Thank you, here is the Readme.md and the folder with the files (folder is called CSS), then within the CSS folder I have the index.html file and the linked CSS file.
web projects can get very complicated quickly, and so having common sense naming conventions and folder hierarchies that make sense even when its 2am and you are on a deadline is really important. I wouldn’t be doing my job right if, at this point, i didn’t encourage you to move your index.html our of your css folder and put it on the same level as that readme file.
it should always go like this, structure wise for a simple static site - commonsense foldernames, everything lowercase. index.html at the top, all assets in their proper place, all lowercase filenames, all the same file extensions, nice and tidy
and so on. you get the idea. change your folder structure around and commit to github, and then i think you will find that it will work. at the moment, you’re not pointing our robots to find the index.html because you have tucked it away in a subfolder.
