Recent searches
Search options
Random stream of thoughts relating the source code of my website: I want to make the repository public again. However, there are a few problems:
1. I used to have private posts. That's why I made it private in first place. I rarely used them, but I did use them.
2. There's over 20 000 commits with enigmatic names, especially due to my backend system creating commits for every single change.
3. The repository is quite large (over 400 MB) since I used to store images on it before.
3 is not the largest issue, but 1 and 2 definitely are. I see a few options:
a. New repo with all commits after the newest after removing private posts.
b. New repo with everything before and after private posts.
c. Somehow filter the repo and remove everything private (have no idea)
d. New public repo with the current state, keep current private and archive it.
I'm leaning towards d, or just keeping the way it is. But I don't know. Maybe someone has an idea.
@hacdias I went for c. some years ago and used a combination of BFG Repo-Cleaner and git-filter-repo. That worked well.
https://rtyley.github.io/bfg-repo-cleaner/
https://github.com/newren/git-filter-repo
@juni thanks for the tools. My problem with that strategy is not knowing exactly which are the files 