The only way that I know to completely reduce back-and-forths on a pull request is to not use them.
Instead, embracing practices as Continuous Delivery/Deployment in main branch + Feature Toggles + Pair Programming.
Even though it might seem cool, it comes with a lot of different challenges and assumptions, and done wrong can cause disasters.
Being honest, after I have been involved in three teams doing it, I won't come back to PR. I prefer the benefits and pains that CD brings over the pains and benefits of Pull-Requests.
But meanwhile you still need to use PR, this reference is a good starting point to get the process more smooth and less frustrating 😁
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.
The only way that I know to completely reduce back-and-forths on a pull request is to not use them.
Instead, embracing practices as Continuous Delivery/Deployment in main branch + Feature Toggles + Pair Programming.
Even though it might seem cool, it comes with a lot of different challenges and assumptions, and done wrong can cause disasters.
Being honest, after I have been involved in three teams doing it, I won't come back to PR. I prefer the benefits and pains that CD brings over the pains and benefits of Pull-Requests.
But meanwhile you still need to use PR, this reference is a good starting point to get the process more smooth and less frustrating 😁