Hacker News
points by moron4hire 3 days ago | 0 comments
This is a problem of requiring PRs for everything, not of putting tasks in the repo.
[–] Cthulhu_ 3 days ago
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`.

[–] paxy 3 days ago
PRs or not, git workflows are always going to be many orders of magnitude slower than simple database reads/writes.
Hacker News