I would necessarily call this a bug but I did find it a bit surprising so I thought I would see if it’s expected behavior. I had one repo open doing some work for a client when another client had some “small but emergency” items that needed attending so I opened their repo in the same window, did some commits/pushes, closed their repo, and went back to what I was doing which involved trying to get the CI/CD pipeline working so bunch of small commits where I’d use the same commit message one upping the “part #” at the end. Turns out the history is global to Merge and threw me for a loop for a second.
Like I said, not necessarily a bug but thought I’d check to see if that’s the expected behavior.