Hacker News new | ask | show | jobs
by xena 3322 days ago
I personally have a repo full of old code and move projects there once I'm done with them: https://github.com/Xe/code
1 comments

Why'd you want to do that? You loose your history etc.
I don't understand that fixation on "history", it was helpful couple of times to find who did change and if there is ticketing system with attached ticket then I get some context. But bunch of diffs does not matter and for side project that I am doing on my own what I care for is current state not that I changed name of class and then changed it again two days later. Maybe I am missing something?
Not necessarily - there's multiple ways to collapse at least one branch's history into another repo e.g. from https://github.com/arkie/proto

  read repo; git fetch ../$repo/ master:$repo; git push origin $repo

    git remote remove origin

    git remote add origin <dead_repo_url>