alt Hacker NewsThis is a problem of requiring PRs for everything, not of putting tasks in the repo.
Replies
paxy • today at 2:01 PM
PRs or not, git workflows are always going to be many orders of magnitude slower than simple database reads/writes.
This is a problem of requiring PRs for everything, not of putting tasks in the repo.
PRs or not, git workflows are always going to be many orders of magnitude slower than simple database reads/writes.
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`.