For a small project it's probably overkill, but when you need to manage a large number of tasks and/or a large number of workers (including product managers, QA, etc.) you need more than a simple text box with some labels.
Think of it as a higher level, more encompassing approach to project management that can include both the technical and non-technical work.
You can create hierarchies of tasks, connect them, assign them, and they are not only for software development like GitHub.
It can also tie in with Gitlab/Github
It's worth watching a Youtube video or two to see if anything resonates than asking strangers blindly on the internet to give us the perfect explanation :)
Project management tools are just a necessary skill even for non-devs, which leaves any large enough project with only two options:
1. Have the devs and non-devs use completely different systems.
2. Have both use the exact same tool, even if that absolutely sucks for the devs.
The second one is bad, the first one is worse. It by definition creates an unnecessary complication in the flow of information, requiring serious effort to overcome. That's why most of us have horror stories about Jira, Asana, and the likes. The hatred of that one particular tool we happen to be using right now unites us all. Whichever tool you're currently using is always the worst one, right until the moment you're forced into using a different one.
So, you as an individual might want to put up with one of these horrible options you're already familiar with, or you might use something you actually enjoy. But beware: if you go down the more enjoyable path, you are perpetually gonna be reminded it's not the "real deal". GitHub can't do everything a proper tool can, and you're gonna miss having those "advanced" options at some point, even if you hate to admit that to yourself.
Then again, I might just be projecting.