The person seems relatively young age wise and thus is probably in the process of learning things.
Edit: the comment was not about code quality but credentials, explained below.
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/
This is also good for you to decide what can be public and what should remain private. 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.
I was more referring to the apparent accidental inclusion of completely unrelated access credentials. That’s something they’re now learning the hard way.
Maybe don’t get in the habit of committing everything in your learning repo, just in case you’ve accidentally saved something else there.
> I was more referring to the apparent accidental inclusion of completely unrelated access credentials. That’s something they’re now learning the hard way.
That's a good point, though! Comment edited, thank you for the clarification.
Edit: the comment was not about code quality but credentials, explained below.
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/
This is also good for you to decide what can be public and what should remain private. 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.