The posted link is to the error page. https://teams.microsoft.com works in FF stable.

Oh wow, I clicked on that link on mobile and was unable to go back. Pressing the back button just redirected to the same page over and over again. Usually you only see that on malicious ad sites.

Microsoft's tech forum pages have been highjacking the back button for years now. It's really despicable...

Microsoft's largely useless support site does the same thing. There's something weird afoot in that organization.

If you don't know already, long press on the back button solves the problem.

Nope - "We're sorry—we've run into an issue."

Nope, it doesn't. FF stable on MacOS.

Teams is, was, and will be the absolut worst. They only won, because it's bundled into MSO.

Doesn't work on stable 110.0.1 (64-bit).

EF 6 had an interesting take on this problem. If two migrations had the same parent (aka we both branched and added a migration), whoever merged second would have to generate a "merge" migration to resolve the conflict. It wasn't the most elegant solution, or even a solution period, but it made the problem explicit. This happened because the full schema model was serialized and encoded into the migration journal table.

This is the actual model of git.

You try to push on a remote after somebody else, you have to create a merge commit.

But it would be nice to have a rebase to keep linearity in your history.