PSA: I’m not terrified of rebase, yet it’s good to know this:

https://docs.github.com/en/get-started/using-git/about-git-r...

> Warning - Because changing your commit history can make things difficult for everyone else using the repository, it's considered bad practice to rebase commits when you've already pushed to a repository.

A similar warning is in Atlassian docs.

▲

ongy 5 hours ago | parent | next [-]

I think a large part of this is about how a branch is expected to be used.

Branches that people are expected to track (i.e. pull from or merge into their regularly) should never rebase/force-push.

Branches that are short-lived or only exist to represent some state can do so quite often.

	▲	xlii 4 hours ago \| parent \| next [-]
		Also branches that are write-only by a single person by consensus. E.g. "personal" PR branches that are not supposed to be modified by anyone but owner.
	▲	thibaut_barrere 5 hours ago \| parent \| prev [-]
		It is this, plus more: - the web tooling must react properly to this (as GH does mostly) - comments done at the commit level are complicated to track - and given the reach of tools like GH, people shooting their own foot with this is (even experienced ones) most likely generate a decent level of support for these tools teams

▲

mr_mitm 3 hours ago | parent | prev [-]

Is there a reason why that recommendation cannot be changed to "don't ever force push unless you are certain no one else has fetched this branch"?