Please don't be overly negative about low quality code in their personal repo, which might be more or less of a scratch pad, since that is very demotivating.
That said, personally I'd suggest keeping one's code in separate repos with corresponding READMEs, since otherwise it's pretty hard to realize what you were doing a few months down the line: https://www.readme-templates.com/
Furthermore, separate repos are a good idea if you ever want any CI introduced for the project, or build any libraries from it. There's nothing wrong with monorepos, but even those are typically used within the context of a particular project or group of projects.
Maybe don’t get in the habit of committing everything in your learning repo, just in case you’ve accidentally saved something else there.
That's a good point, though! Comment edited.
What you need to do is an interactive rebase, go through all commits, and remove the files by editing the original commits. You can do this with git rebase -i but it is very labor intensive and requires a lot of concentration to get right.
Afterwards your local history will have diverged from GitHub and you need to git push -f to replace the commit history on GitHub with that of your local repository.
It might be a good idea to make the repository private until you have changed all of your passwords and made sure there is no such material in the repository’s history. That doesn’t help if someone already cloned it, though.
Good luck in any case. Hope you have strong passwords and 2FA on your Steam and Gmail.
https://github.com/SriLikesToSing/practice/blob/master/tinke...
What other interesting things could one find in this repository?