Open Source is sometimes described as "anyone can contribute", but that's an oversimplification. Open Source projects always have a gatekeeper or small community of gatekeepers who decide which contributions are actually incorporated into the project and which are rejected as not up to snuff or straight up bad ideas or whatever.

That's what you meant by your first question, right? Not "how do I hide the code of future changes" but "how do I retain control over what code is added to my repo", correct?

Even if you meant it the other way, you could theoretically do that. Open Source one version and then never release any newer versions.

[–] LemmyQuest@lemm.ee 2 points 1 year ago (6 children)

No, I meant that I wanted to hide old commit history.

[–] TootSweet@lemmy.world 8 points 1 year ago (3 children)

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.)

[–] henrikx@lemmy.dbzer0.com 9 points 1 year ago (2 children)

It's worth noting that you can rewrite history after the fact with Git

[–] TootSweet@lemmy.world 2 points 1 year ago

...if you hate anyone who might have a clone that they want to pull to later.

[–] navi@lemmy.tespia.org 1 points 1 year ago

Force push main with one giant squash commit.

load more comments (2 replies)

load more comments (4 replies)