Hacker News
points by jurgenburgen 4 days ago | 0 comments
Tickets change faster than code. Having to create a PR to update a ticket sounds like a bureaucratic nightmare.
[–] jm4 3 days ago
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.
[–] moron4hire 3 days ago
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.
[–] Squeeeez 3 days ago
Then you go the nanoservice route, with double the repos!