As many of you asked for, we've finally made the repository public and will continue developing it in public from now on.
This took us some time, but you can now read our announcement for more details[0].
Thanks everybody for the support so far, and I welcome you all to interact with the repo, join the discussion, or even contribute.
A possibly noteworthy detail as it's been discussed on HN here a bunch, we've settled with the DCO[1] for contributions.
Also, happy to answer any questions!
[1]: https://developercertificate.org
Disclaimer: Work at Spacelift, and currently temporary Technical Lead of the OpenTF Project, until it's committee-steered.
I've made sure via repo config that only squash commits are enabled from now on, so this will not happen again. Thanks for the feedback!
The "real" solution is making the developers aware of the issue and cleanup up their history before doing an MR.
For a start, it's easy to review, and easier to disect if something breaks.
When messy git history is provided (i.e. a history of the developer fixing their own code that they missed), squashing can be a reasonable fallback. But it's never the best option, IMHO.
It's a separate project from git [0].