Tickets change faster than code. Having to create a PR to update a ticket sounds like a bureaucratic nightmare.
Then you go the nanoservice route, with double the repos!
This is a problem of requiring PRs for everything, not of putting tasks in the repo.
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.