I build things with my hands. The human behind Shift - https://laravelshift.com, master of Git - https://gettinggit.com, and author of "BaseCode" - https://basecodefieldguide.com
The reason people shy away from rebase is because it rewrites history - meaning it changes the commit SHAs. So if you're sharing your work with others, that can be a problem.
It's likely this consultant was the victim of a force push and made a sweeping statement to never use rebase again. We've all been there. It's frustrating.
Being mindful of which commands, like rebase, can rewrite history resolves this issue. Then you can use it appropriately. For example, I use rebase often. But I do so at the end - right before merging - so I limit the chance for it to affect other developers.
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 reason people shy away from
rebaseis because it rewrites history - meaning it changes the commit SHAs. So if you're sharing your work with others, that can be a problem.It's likely this consultant was the victim of a force push and made a sweeping statement to never use
rebaseagain. We've all been there. It's frustrating.Being mindful of which commands, like
rebase, can rewrite history resolves this issue. Then you can use it appropriately. For example, I userebaseoften. But I do so at the end - right before merging - so I limit the chance for it to affect other developers.