The first one is infuriating. That error message is good for nothing. Happens frequently that a colleague does a pull, as instructed, after forgetting to push with force after rebasing or amending a commit.
Faintly remember a discussing on the mailing list where a suggestion to improve it was shot down for some dumb reason.
I would guess it was “shot down” because it is evidence that the user is not paying attention. After a rebase, git tells you that you need to force push. So a person would have to ignore that message, get distracted, and then try to pull when the changes they had previously made haven’t even been pushed. Then if that’s happening “over and over” (“frequently”) this person isn’t learning from the tool’s feedback on what to do and is instead just doing random things. I would suspect the git team is not fond of people doing random things and wanting them to change the tool to accommodate that.
Faintly remember a discussing on the mailing list where a suggestion to improve it was shot down for some dumb reason.