if that doesn't work, could also try reverting to see if you can get it back to a working state. then two options. maybe do a testing repo with a gh-pages branch and see if it persists in a new repo (assuming the revert fixes it)
or revert the master and gh-pages and make a testing folder named docs and use the fact you can change the branch that gh-pages renders for testing but you can go back to a working version for recruiters.
or third option, revert gh-pages back to something working and just try to get master branch working and switch gh-pages to render master for testing. then you can go back to gh-pages as neccessary.
the new repo option would prob be best if it's a cache issue