Your 50+ file change PR makes you stand out to your manager. Good job.

You just caused merge conflicts across the board.

Please, work in smaller steps.
Please, work in safer steps.
Yes, this means you will need to take many more steps.
But they’re smaller, so can be reviewed much faster.
Better yet, pair so it gets reviewed while it’s written and avoid the costly waste of time waiting for others to review such a small change.

By putting 50+ file changes into 1 giant PR (usually with 1 commit) you are shifting your lack of discipline and care onto everyone else.

By making smaller safer steps, every step of the way should be deployable, tested, understandable, etc. And you’re helping others follow your line of thinking.

Most important of all, get those changes merged in.

Others need to see the changes in the code they’re working on before your 50+ file change causes merge conflicts, reduces peoples willingness to do large refactors, etc.