Closed PeterGhimself closed 7 years ago
GREAT SUCCESS!
By the way, instead of reverting the revert merge commit what I did was:
checkout master and revert to this merge commit
git reset --hard d634323c00df0195de9de2631ed01fcae0a57f81
merge this branch into master
git merge reorganizeFolderStructure-12
force (override commit history) push to master, so that that ugly revert merge commit would be taken out of the commit history
git push --force
This PR is related to issue #12 and a redemption PR for the break in #13
The problem
When merging #13 I noticed that going to
spaceconcordia.github.io
brought me to a page that just rendered theREADME
file. I reverted the merge commit on master right away after seeing that and our site was back to normal: servingindex.html
first. Apparently, by default github pages will search for anyindex.html
within the root directory and load it, and if it fails to find one it will search for the next best thing and load that instead.The solution
What I have done here is simply put the
index.html
out ofsrc/html/
and back in the root folder and updated all the references toindex.html
and withinhtml.index
, which should fix theREADME
showing up in our homepage instead of theindex.html
page. This required me to also make some changes toexpandableLinks.js
. I also fixed some unupdated references tomap.js
.About merging
~~I understand that this branch can't automatically merge yet, but I believe all I have to do is revert the revert merge commit I made to
master
, and then I should be able to merge this without any issues. Of course, if I revert the commit on master, then the site will be bringing visitors to our README file. I'll wait till I get your comments/approvals for this PR, then I'll revert the revert merge commit and then swiftly merge this branch to hopefully resolve the issue.~~