this post was submitted on 29 Mar 2024
10 points (72.7% liked)
Open Source
31072 readers
804 users here now
All about open source! Feel free to ask questions, and share news, and interesting stuff!
Useful Links
- Open Source Initiative
- Free Software Foundation
- Electronic Frontier Foundation
- Software Freedom Conservancy
- It's FOSS
- Android FOSS Apps Megathread
Rules
- Posts must be relevant to the open source ideology
- No NSFW content
- No hate speech, bigotry, etc
Related Communities
Community icon from opensource.org, but we are not affiliated with them.
founded 5 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
No, I meant that I wanted to hide old commit history.
Ah! Yes. No reason why you couldn't. It would require making a new repo, copying the files into the new repo, and committing in one big commit before pushing to gitlab, but yeah. Definitely doable.
(I basically always do this myself. I don't start the Git repo until I want to Open Source it. So when I first Open Source it, it's a "complete" (or at least "minimum-viable-product") project and there's only one commit. Every commit I make and push thereafter is public, but there aren't any from before my first push/publish.)
It's worth noting that you can rewrite history after the fact with Git
...if you hate anyone who might have a clone that they want to pull to later.
Force push main with one giant squash commit.
You can always just reset your git history:
You'd have to collapse all branches not just one, and remove all tags, in order to clear the whole graph.
And of course you have to be allowed to – GitHub can have protected branches, protected tags, and force push protection.
Assuming you're the repo owner and can do all that it still would't affect other people's already existing clones, only new clones.