📁 Git* solves the problem of managing files

The thing you get with Git* is a sane way to manage files:

• organization (team/repo/directories)
• documentation (excellent support for Markdown)
• efficient navigatation (links in READMEs and other markdown files)
• history (who changed what when)
• collaboration (issues, pull requests)
• distributed (anyone can work anywhere)
• automation (continuous integreation (CI), continuous deployment (CD), hooks, etc.)
• reviews (PRs)
• workflow (enforces workflow such as requiring PRs, approvals, etc.)
• versions (feature and maintenance branches)
• releases (built in way to do formal releases)
• security (granular access controls and workflow permissions, bank level security for web access (https), and better for Git operations (ssh keys))

Git* is not primarily a way to manage projects, but rather a way to manage and collaborate around files, with some project management thrown in. It is centered around the work, which is the main point.

Other tools have more advanced project management features, which are needed at times. But they are missing a key ingredient: tight integration with your files. The closer you can keep your project management and other metadata to the actual work, the better.