That is not something Github is doing, it's fundamental to how git works that different commits have different hashes - and rebasing creates different commits (

That is not something Github is doing, it's fundamental to how git works that different commits have different hashes - and rebasing creates different commits (they have different parents). Not rebase-merging would probably suit your workflow better.