Your view of GitHub is undoubtedly wrong. Deleting the codebase and issues is the wrong approach. No matter how long that list gets, it’s good that issues have been documented. It’s good that the community is aware of them.
The purpose of having a public repo is not only that it can be shared, but that it can also be forked. There are better programmers out there, with more care, more motivation to take things to the next level. If you don’t have time, that happens, but it allows the project to continue.
You can merge their changes in, give them control of your repo, or stop maintaining and the public will use a forked version.
You shouldn’t feel a slave to your project. Also, while it’s good to commit early and often, you should perform various levels of testing before you conclude that it’s at a state that no longer needs to be worked on. Issues that are bugs often are because we as programmers did not test enough (that is on us)