The way pull requests and commits work in the OpenJDK repository -- a bot squashes each pull request into one commit: https://github.com/openjdk/jdk/pull/31120#issuecomment-51378...

The final singular commit is cc278db (8389219: Implement JEP 401: Value Objects (Preview), 2026-07-31) https://github.com/openjdk/jdk/commit/cc278dbb8a1ca0754d5842...

▲

fulafel 3 days ago | parent [-]

Is there a writeup on why they choose to destroy the history?

▲

jerven 3 days ago | parent [-]

You can recover the history using their tooling build on top of their bugtracker and GitHub. Specifically they capture the discussions and all small changes over time in their skara tools and are prepared to leave GitHub if needed. They had multi de adres experience and had multiple prior code repos. Still do if i understand as the Oracle team has the sun and bea code repositories pre openjdk preserved.

	▲	fulafel 2 days ago \| parent \| next [-]
		Hmm. Is this about Github or Git? Dependency on Github seems tangential to treating Git as a first class record of history. edit: rereading, I guess the implication is that there's tooling built on top of Github outside of Git, so Git history is indeed not meant to be contain some things.
	▲	J-Kuhn 2 days ago \| parent \| prev [-]
		Before openjdk did move to github, they made sure they had a solution for those problems: * Contributors without github accounts * Moving away from github (when needed) * No vendor lock-in for github stuff. I personally think, this is a good idea - a lot of work, but may be worth it in the long run.