To give you a concrete reason why you should care to preserve the exact history and why it’s a matter of trust: in your paper, you reported the pinned SHA head of the benchmarks you ran. When you destroy the history you make it hard for people to duplicate your benchmark results. Why report the SHA if you are going to destroy the history?
replyhttps://github.com/bendlang/bend/blob/80b6539bc57621633ca68e...
Erm, because it looks weird? Do you know any other language projects that squash their repos down to 1 commit? That's a destruction of trust, which is kinda important if you want people to build on your language.
replyVirtually everyone has AI slop in the commit history. No one's judging you for the commit history. Everyone's code smells, but the fact that you're ashamed/hiding it is... odd.
> there's a lot of personal info
You should know that force pushing doesn't hide actual commits; it's trivially viewable if someone just iterates https://github.com/bendlang/bend/activity?ref=main e.g. https://github.com/bendlang/bend/commit/d184863 so like... why bother.
alright, we could try to restore history removing sensitive bits if that's so important. thanks for the feedback
replyProps. G'luck with your project, I know what it's like to work nights & weekends. Unfortunately, first impressions matter.
replyTy! Commit history is back now
replyI for one don't find it strange at all that he squashed the commit history. I suspect many feel similarly. You've demonstrated that you're quite taken aback by it, but without explaining anything wrong with it. It is not a "destruction of trust".
replyI mean... If you wanna build your project on a language that has no auditable history, reproducible builds, artifacts/releases, force pushes and breaks literally EVERY fork/PR, has no way to build or even see v2.0.3, and doesn't have changelogs... then I guess that's cool. You must be a trusting person; I unfortunately am not like that.
reply