if you don't mind, what kinds of metrics is your team tracking to keep an eye on things? It sounds like you'll are a lean team and working hard on some ambitious goals, but if you're not keeping an eye on defect rate, lead-times or some kind of proxy metrics then it's easy to get trapped in a local-maxima of constant fire-fighting.
PR based workflow might actually be overkill for a small team though, so you might consider either:
trunkbaseddevelopment.com/
super short-lived PRs, everyone's mostly working on main
feedback cycles will naturally shrink
pair-programming
assign pairs that are stable for atleast a month
all code that's not pair-programmed must be code-reviewed
budget for lower productivity for a couple of days, but after that you should see much easier information flow in the team.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
if you don't mind, what kinds of metrics is your team tracking to keep an eye on things? It sounds like you'll are a lean team and working hard on some ambitious goals, but if you're not keeping an eye on defect rate, lead-times or some kind of proxy metrics then it's easy to get trapped in a local-maxima of constant fire-fighting.
PR based workflow might actually be overkill for a small team though, so you might consider either:
main