Hacker News Reader

It works great as a solo developer. I've been doing the same thing for the past several months. I couldn't imagine doing it with a team.

This is a problem of requiring PRs for everything, not of putting tasks in the repo.

Counterpoint, many updates would also cause many commits just for keeping tasks updated, adding noise to the project history.

Nothing stopping people from keeping tasks in a separate repository, of course - this would also make it simpler to just allow commits straight to `main`.

PRs or not, git workflows are always going to be many orders of magnitude slower than simple database reads/writes.

Then you go the nanoservice route, with double the repos!