#404 GITHUB PAGES UPDATE#
#404 GITHUB PAGES CODE#

If you created the repository only locally and did not clone it from GitHub, then you'll need to point it to the correct remote repository to push to If not, then the changes haven't been pushed to the remote repository. If it was successful, then it will show up on the commit history on GitHub. You can't push without a commit and you can't commit without adding changes. If you don't push, nothing will change in the remote repository.

push pushes those changes to the remote repository (e.g GitHub).

commit commits the changes locally and makes a 'log entry' with you commit message and changes involved.

add adds changed files to the queue to be commited (in a diff additions are green, deletions are red).

tldr, its needlessly confusing, apparently buggy, and about as unintuitive as humanly possible! lol it just sits there doing nothing, and i saw no push, commit or publish option on the website either. the website sees it (it'll make all changes *red*) but never actually updates it. Yes, but if you *change* or add something it (the app) doesn't give you a 'publish' option, only 'push' and that doesn't seem to work. i had the feeling the web site didn't sync properly with the desktop app half of the time. i also didn't use the app for that in the end, maybe that is buggy too. Make yourself at home!Īnd *then* after nothing worked, i decided to use the themes/templates they dangle in front of your nose all the time : pĪnd that worked right away, wasn't my plan tho, my plan was using my own html code, which i find btw far more pleasing visually than these standard templates. This is roughly what i made, from the link in the OP, i also had background colors and stuff, sobs!

#404 GITHUB PAGES CODE#

and my best guess is that code didn't work, but im not sure. which i personally wrote copy pasted into a html file. Then the repo gets updated and the build system should do its thing. Well for changes you edit the stuff and then add, commit and push (I guess that's what the 'publish' button does? I don't use the GitHub GUI thing.).

I was looking at it from the simpler 'make that repo with index.html' variant point of view. Oh you're using that Jekyll build system. PS: it *is* automatic, you just have to press 'commit' (that obviously didn't work previously, with my 'html file')

#404 GITHUB PAGES UPDATE#

i dont want random links, and stuff, obviously.īut i still dont get how i can update this after i edit it, hopefully thats automatic, i really dont want to delete the whole thing every time i change a single word or line. Low and behold the website is online, but of course doesn't look at all like I'd want. the code keeps changing for no reason lol.Īnd i think maybe thats the issue, github just cant read this html file probably?īecause now i deleted the repo again (i wish i didn't need to do that all the time there must be an easier way to start over lol) I followed this guide basically - in hindsight the site is definitely kinda sus though.Ĭontent://.sbrowser.beta/readinglist/0116023216.mhtmlīut he doesn't tell you anything about coding html so i used this for that.

github.io, added index.html and it worked immediately for me.ĭumb question time, are you using your actual github username? The username in is a placeholder and needs to be you actuall account name.

I just tried it out, created new repository named. It can take about 10 minutes before changes show up according to their documentation. The second problem i don't understand, there must be a way to update a file, or in this case publish a site since that would be the next step its expecting now obviously. Its like I'm in a loop, now i changed the html code again, because I wasn't sure if there wasn't a mistake and pushed it (there is no publish button in that case) and now it says 'your site is ready to be published' in settings but there is no publish button or anything.īasically the first problem seems to be it creates the website, but cant read the file. then it says 'commit successful' (or similar)īut it didn't help, same 404 error as before.

404 github pages