Changing Git history and working with remote repositories?

Question

git

Everyone knows that Git allows you to change the commit history with the commands git reset \ git rebase -i and so on. The question is why it is not recommended to change the history of commits that have already been pushed to a remote repository and how to track that the changes have been pushed so as not to accidentally change the history of such commits?

Answer 1

Because after the rebase, even if nothing has really changed, git creates new commits, and when pushing to a remote server, a conflict will arise that can only be resolved with a force push.
I think it will be faster for you to try it yourself and figure it out.

Answer 2

the reason is simple, git rebuilds all commits after rebase, and they get different hash sums. Roughly speaking, as if you re-wrote all this code in another branch. (With the ensuing conflicts).
So rebase gets in the way a bit most of the time (although if you're 2-3 people and you know what you're doing, rebase is fine).