I would start by trying to fix your own repo code. It isn’t a lot of changes needed.
Move .nojekyll to the public folder.
Update the deploy script to include the -t flag at the end.
I would remove all the redirect code you have as you do not need it. So delete the 404 pages and update the index.html to not have any redirect code inside it.
You can probably keep the .env file and the change to the path from %PUBLIC_URL% to %REACT_APP_PATH% but I’m not sure and didn’t test it. In any case, it isn’t needed so maybe just put it back to the default.
Build it out npm run build and check your output files look correct. The most important is that the .nojekyll is in the output build folder. Then run the deploy script.
Switch to the gh-pages branch and look for the green checkmark on the commit. You can also click the X or checkmark (depending on if it worked or failed) to see the GitHub actions and the log.
That is a fair question in general though. I believe if this was something not for fCC you would need to follow some kind of etiquette here… will leave it to others to fill in this blank as I am not an open source contributor in terms of code…
Seeing as it is a learning project you should try fixing it yourself first. Let us know if you need more help.
As for how we might do it otherwise, I would fork the repo and make the changes then make a PR with the changes. You would review the changes and reject or merge them into your code. This is also great practice and I would highly recommend making PRs to repos like the freeCodeCamp repo which can help you get started with contributing to open-source projects. It is a great way to learn about Git/GitHub and the collaboration workflow.
It is unfortunately a bit of a gray area with regard to the forum rules as we do not allow people to use it for such things. The issue is it becomes an easy way for people to solicit actual work which we do not allow. It would be nice if there was an easier way for people to do collaborations as learning projects through freeCodeCamp but I’m not sure how that would be managed.
I know I have seen people from the forum do some collaborations. I guess people just use chat, Discord, PMs, and so on.
Your directions were so clear, after following them it magically works now.
Though I wish it wasn’t so magically and I understood how you figured this out. But, maybe that’ll come with experience. Or, maybe it’s not necessary to know if I won’t be using gh pages after this. Thanks for the advice on how to make it work on github AND especially the tidbit about not bothering with that anymore.
At first, I didn’t understand why it didn’t work and it really wasn’t until I looked at the failing branch commit I saw what was going on.
I then used Google to look for info about GitHub pages and the .nojekyll file as I saw it wasn’t ending up inside the build folder, so I knew something had to be wrong. I randomly found a script that had the -t flag but it didn’t have any information about what it did. So I went to the node_modules folder and opened the gh-pages.js file to see which flags it has and what they do (they do have a help flag as well). I saw the .option('-t, --dotfiles', 'Include dotfiles') line, and then it was obvious why it wasn’t getting pushed.
As for the other changes, they were more just to cover all bases and when it worked I didn’t bother to see if they were needed or not.